openspec-sync-specs

Merging delta specs into main specs without overwriting content requires reading both delta and main spec files, then applying intent-driven updates that add, modify, remove, or rename requirement blocks while preserving unrelated content.

A delta spec is a targeted specification file expressing intent like added, modified, or removed requirements. You need to sync it into a canonical main spec when changes are staged in openspec repositories and must be reflected in the main specification.

Applying intent-driven spec updates involves reading delta spec changes and applying precise edits to main specs per-capability, adding scenarios or requirements based on the expressed intent to ensure accurate content updates.

OpenSpec sync handles ambiguous changes by prompting the user to choose the correct change during the merge process, ensuring the correct intent is applied and preventing incorrect modifications to the canonical main specs.

Yes, you can create new spec files when syncing delta specs. The sync process detects when capabilities are new and automatically creates the corresponding spec files to apply the delta changes.

Merged spec changes are idempotent and auditable. The process produces a summary of applied additions, modifications, removals, and renames, ensuring updates are reviewable and repeatable without duplicating requirement blocks.