openspec-sync-specs

To merge delta specs into main specs without losing existing requirements, apply changes per-capability to add, modify, or rename requirements while preserving unrelated content. This deterministic merge updates the main specs idempotently without archiving the delta.

A delta spec workflow for change management tracks incremental requirement changes separately in a delta directory, then merges them into main capability specs. This preserves traceability and allows guarded, interactive updates before finalizing modifications.

Yes, you can automate applying spec changes from a delta folder to main specs. The process reads delta structures and idempotently updates main capability specs, prompting for user input only when choices are needed to prevent unintended changes.

Merging delta specs does not archive or delete the original delta files. It applies the added, modified, or renamed requirements directly to the main specs, ensuring the changes are traceable while keeping the delta intact for reference.

Interactive merging handles conflicting requirement updates by enforcing guardrails that prompt for user input when needed. This validates results and prevents unintended changes, ensuring deterministic and idempotent updates to the main specs.