openspec-sync-specs

To merge delta specs without losing content, apply delta changes from openspec/changes/<name>/specs to corresponding main specs, preserving unrelated requirements. The process adds, modifies, removes, or renames requirements while keeping non-delta content intact.

Delta specs represent incremental changes to a main specification set. They define specific updates—adding, modifying, removing, or renaming requirements—so you can safely apply targeted changes without rewriting the entire specification.

Yes, merging delta specs creates new main specs automatically when they do not exist yet. The process applies the delta changes to the corresponding main specs and outputs a summary of changes alongside a refreshed specification catalog.

When context is ambiguous during a spec merge, the process validates changes with guardrails and prompts for user input. This prevents regressions and ensures requirements are added, modified, or removed correctly before finalizing.

Yes, the spec merge process operates without external dependencies. It directly reads delta specifications from the openspec/changes directory, applies validation guardrails, and outputs the updated main specs and refreshed catalog autonomously.

The best way to archive delta specs after merging is to review the resulting updates and refreshed specification catalog first. Once the applied changes are verified, you can safely archive the processed delta specifications from the openspec/changes directory.