openspec-sync-specs

To merge specification changes into a main spec, apply added, modified, removed, and renamed requirements selectively from a delta spec. This syncs evolving product requirements without manual copy-pasting, preserving all existing unaffected details in the main file.

A delta spec is a structured file capturing iterative changes to product requirements. You need it when evolving feature specifications on a separate branch, allowing you to isolate modifications before synchronizing them back into the main specification document.

Sync updated requirements by running the openspec-sync-specs process, which intelligently merges delta changes into the main spec. It applies only the new or modified scenarios from your branch, preserving all other existing details within the target requirement.

Yes, you need the openspec CLI installed to synchronize specifications between branches. The CLI is required to list and manage specification deltas and main files, providing the contextual input needed to apply the targeted requirement changes.

Yes, you can selectively apply removed or renamed requirements when syncing specs. The intelligent merging process supports applying added, modified, removed, and renamed requirement changes individually from the delta spec to the main specification.

The best way to manage evolving product specifications is using a structured documentation system with openspec. Teams iterate using delta specs for feature changes, then sync only those specific requirement modifications back to the main spec, avoiding manual merge conflicts.