openspec-sync-specs

To sync delta specs to main OpenSpec specification files, the skill reads both delta and main markdown files, prompts you to select a named change if ambiguous, and intelligently merges additions, modifications, removals, and renames while preserving unrelated content.

An idempotent merge for OpenSpec requirement changes applies delta modifications, additions, removals, and renames to main specs safely, ensuring that running the sync operation multiple times produces the same result without overwriting existing unspecified content.

To apply renamed and removed requirements across multiple capability specs, the skill parses delta spec sections and selectively targets main spec files for updates, prompting you to choose a specific change when multiple named changes are detected.

Yes, you can create new OpenSpec capability spec files from a delta change. The sync skill automatically generates the missing capability spec files, adds Purpose placeholders, and provides a concise summary of what changed for review.

Syncing OpenSpec delta specs does not overwrite existing scenarios and descriptions. The intelligent merge process applies only intended additions, modifications, removals, or renames while strictly preserving other unspecified content in the main spec markdown files.