openspec-sync-specs

To sync delta specs into main OpenSpec spec files, the skill reads delta and main spec markdown to intelligently merge changes per capability, preserving unrelated content while adding, modifying, or removing requirements.

Yes, automatic merging applies only the specific requirement updates from the delta file, such as renaming or modifying, while preserving existing scenarios and unrelated content in the main specification markdown.

The best way to apply per-capability delta changes is using an agent-driven process that reads each delta file, creates new spec files when needed, and produces an auditable summary of all applied updates.

No, repeated spec synchronization runs do not produce divergent results because the merging process is designed to be idempotent, ensuring consistent main spec files across multiple identical delta applications.

Handling requirement additions and renames involves reading the delta specification markdown, applying the targeted changes to the main spec file, and generating a clear summary of the updated capability requirements.

New spec files need to be created during delta sync when a delta specification introduces a capability or requirement set that does not yet exist in the main OpenSpec specs directory.