openspec-sync-specs

Merge delta spec changes into main OpenSpec specifications without archiving the change.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/germainlefebvre4/cvwonder-forms --skill openspec-sync-specs-germainlefebvre4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/germainlefebvre4/cvwonder-forms/tree/main/.gemini/skills/openspec-sync-specs
Command: npx skills add https://github.com/germainlefebvre4/cvwonder-forms --skill openspec-sync-specs-germainlefebvre4

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) to main specs through intelligent merging, so partial updates like adding a single scenario do not require rewriting entire requirement blocks. ## Core Features & Use Cases - Intelligent Delta Merging: Reads delta specs and applies only the stated changes to main specs, preserving existing content not mentioned in the delta. - Change Selection & Validation: Resolves the target change from context or prompts the user, and uses openspec status --json output as the authoritative source of delta spec paths. - Store-Aware Operation: Supports registered OpenSpec stores via --store <id> flags so specs in standalone repos can be synced. - Use Case: After drafting a change proposal with delta specs for a billing capability, run the sync to update the main billing spec with the new requirements while keeping the change active for continued implementation. ## Quick Start Ask the assistant to sync the delta specs from a named change into the main specs, for example by saying "sync the specs from the add-billing 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 to main specs in OpenSpec?

Run the sync workflow with a change name, or let it infer the change from context. It reads the delta specs listed in the openspec status JSON output and merges their ADDED, MODIFIED, REMOVED, and RENAMED requirements into the main specs.

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

Syncing updates main specs with delta changes while keeping the change active for further work. Archiving also applies the deltas but then closes and moves the change out of the active set, so sync is used when implementation is still in progress.

Does openspec sync require the openspec CLI?

Yes, the workflow depends on the openspec CLI for commands like status, list, and instructions. It uses the JSON output of these commands to locate delta spec paths and the main specs root rather than guessing file locations.

Can I sync only some delta specs instead of all of them?

Yes, you can name an explicit subset of delta spec paths to sync, and only those will be applied. The named paths must exist in the status output's existingOutputPaths list; unknown paths are reported and the sync stops.

What happens if a MODIFIED requirement only adds one scenario?

The merge is intelligent and partial: only the new scenario is added to the existing requirement in the main spec. Existing scenarios and content not mentioned in the delta are preserved, so you never need to copy the full requirement.