openspec-sync-specs

Merging delta specs applies changes from openspec/changes to your main specs directory. The sync-specs workflow reads delta specs, intelligently merges ADDED, MODIFIED, REMOVED, and RENAMED requirements, and updates authoritative specs while preserving unrelated content—all without archiving the delta.

Synchronization applies all tracked changes from delta specs to main specs with guided selection when multiple deltas exist. The process enforces merging rules for each change type, maintains spec integrity, and creates an auditable record of what changed and why.

The workflow prompts you to select which delta spec to merge when multiple exist, preventing accidental bulk changes. This guided approach ensures you control exactly which changes apply to your main specs in each sync operation.

No. The sync respects REMOVED and RENAMED change types, updating or removing requirements as the delta specifies. Unrelated content in main specs remains untouched; only requirements affected by the delta are modified.

Delta specs must be organized under openspec/changes directory with a corresponding main specs directory. The sync reads from changes and writes updates to main specs, so both directory structures and spec files need to exist before running the merge.