openspec-sync-specs

To merge OpenSpec delta changes, provide the delta change name to an agent-driven process that applies updates while preserving unrelated content. It intelligently merges modifications across capabilities and prompts for input when context is unclear.

An OpenSpec delta merge integrates incremental spec updates into main specs using an agent-driven process. It supports ADDED, MODIFIED, REMOVED, and RENAMED changes with safeguards to prevent unintended overwrites of existing content.

Yes, when applying OpenSpec spec changes, the merge process automatically creates missing specs if needed. This ensures new capabilities introduced by the delta are properly generated and documented during the update.

The best way to apply OpenSpec delta changes safely is using guarded operations. The agent-driven merge supports safeguards that prevent unintended overwrites, preserving existing content while applying targeted modifications across capabilities.

The OpenSpec merge process prompts for input when context is unclear during the delta update. This intelligent, agent-driven approach ensures ambiguous changes are clarified before merging, preventing incorrect modifications to main specs.

Manual validation is reduced because the merge process returns a summary of updated capabilities and changes. This automated summary provides the necessary validation feedback by detailing exactly what was modified, added, or removed.