openspec-sync-specs

To merge delta specs into main specs safely, run the delta-sync command to read changes from openspec/changes and apply them to openspec/specs. This process validates the delta structure and handles conflicts gracefully without overwriting non-delta content.

Delta-spec merging is the process of applying incremental changes from separate delta files into primary specifications. You need it when delta specifications evolve separately from main specs and you want to apply safe, traceable updates without archiving the original delta.

Yes, you can create main specs from scratch using a delta spec. The merge process supports safe creation and evolution by generating new corresponding entries in openspec/specs for new capabilities that do not yet exist in the main specifications.

Merging delta specs preserves existing main spec content not mentioned in the delta. It targets specific delta changes to update or create corresponding entries, ensuring idempotent updates that retain all untouched non-delta content.

Delta-spec merging handles missing context by prompting for input when needed, and it handles conflicts gracefully by validating the delta structure before applying changes. It also retains a history of applied changes for safe, traceable updates.

The best way to manage incremental spec changes across multiple capabilities is using intelligent delta-merge. It reads delta specs from openspec/changes and updates multiple corresponding entries in openspec/specs, supporting partial updates and preserving non-delta content.