openspec-sync-specs

To merge delta specs into main OpenSpec specs, read both the delta and main spec files, then apply only the added, modified, removed, or renamed requirement blocks. This preserves existing scenarios and untouched content while keeping the main specs up to date.

When a main spec file does not exist yet, the delta synchronization process automatically creates the missing `openspec/specs/<capability>/spec.md` file. This ensures new capabilities are properly initialized while applying the delta requirements.

Yes, the delta spec synchronization produces idempotent results, meaning applying the same delta merge multiple times will consistently yield the same final main spec state. It also provides a summary output of the applied changes.

When a change name is missing or ambiguous during spec synchronization, the process prompts you to choose the correct change. This guardrail ensures the correct delta branch or folder is applied to the active specs.

The best way to update specific requirements is to use a delta merge that edits only the requirement blocks mentioned in the delta. It reads the corresponding main spec and preserves all other content that is not referenced by the change.