openspec-sync-specs

Intelligent delta merging applies ADDED, MODIFIED, REMOVED, and RENAMED changes from delta specs to main specs while preserving existing content not mentioned in the delta. This avoids overwriting the main specification during the sync process.

When multiple delta specs are available for a change, the sync process prompts the user to select the correct change. This ambiguity handling avoids guesswork and ensures the correct delta spec is applied to the main specs.

To sync openspec change requirements to a new main spec, run the delta-sync command with the desired change name. The tool reads delta specs from openspec/changes and automatically creates new main specs at openspec/specs if they are currently missing.

Yes, delta spec merging handles removed and renamed requirements. The intelligent merge applies ADDED, MODIFIED, REMOVED, and RENAMED changes to the main specs and reports a summary of all performed changes after the sync completes.

The best way to apply incremental spec changes in openspec is to use a delta-sync command. It reads both delta and main specs before making changes, merges the requirements intelligently, and generates a summary of the performed modifications.