openspec-sync-specs

Merge delta spec changes into main OpenSpec capability specifications.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/pvtvv/climber-app --skill openspec-sync-specs-pvtvv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/pvtvv/climber-app/tree/main/.cursor/skills/openspec-sync-specs
Command: npx skills add https://github.com/pvtvv/climber-app --skill openspec-sync-specs-pvtvv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specifications in sync with change proposals is tedious and error-prone when done by hand. This Skill applies delta specs (ADDED, MODIFIED, REMOVED, RENAMED requirements) from an OpenSpec change directly into the main specs with intelligent merging, without archiving the change. ## Core Features & Use Cases - Intelligent Requirement Merging: Adds new requirements, updates modified ones, removes deprecated ones, and renames requirements while preserving untouched content and ordering. - Store-Aware Operation: Discovers registered OpenSpec stores and scopes all CLI commands to the correct specs root via --store flags. - Safe Capability Retirement: Deletes a capability's spec.md only when strict conditions hold, including the retire_capabilities: true marker, and reports recovery guidance. - Validation & Summary: Runs openspec validate --specs after syncing and reports exactly which capabilities and requirements changed. - Use Case: After drafting a change with delta specs for a billing capability, ask the agent to sync those deltas into the main specs so the canonical documentation reflects the proposed behavior while the change stays active. ## Quick Start Ask the agent to sync the delta specs from a named change into the main specs, for example by saying "sync the specs from the add-billing-invoices change".

Frequently Asked Questions about openspec-sync-specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync delta specs into main specs with OpenSpec?▼

Provide a change name or let the agent infer it from context. The skill reads the delta specs listed in the change's status JSON, merges ADDED, MODIFIED, REMOVED, and RENAMED requirements into the main specs, then validates the result with openspec validate.

What is the difference between syncing specs and archiving a change in OpenSpec?▼

Syncing updates the main specs while keeping the change active for further work. Archiving also applies the deltas but then closes and archives the change, so sync is used when implementation is still in progress.

Does openspec sync work with registered stores?▼

Yes. The skill runs openspec store list to discover registered store ids and passes --store <id> on all commands that read or write specs and changes. Without a store, commands act on the nearest local openspec/ root.

When does OpenSpec delete a capability's spec.md during sync?▼

The spec file is deleted only when removing requirements leaves no requirement blocks, the spec remains well-formed, the change declares retire_capabilities: true, and the file resolves inside the real specs root. Otherwise the sync stops and reports the blocking condition.

Can I sync only some delta specs from a change?▼

Yes. A caller can narrow the sync to an explicit subset of paths from artifactPaths.specs.existingOutputPaths. The skill syncs only those named paths and never widens the selection back to the full list.