openspec-sync-specs

Merging OpenSpec delta specs into the main specification set involves reading change branches and applying added, modified, removed, or renamed requirements to the canonical files while preserving untouched content.

Syncing delta specs does not blindly overwrite existing requirements. It updates only the affected requirement blocks so existing scenarios and content stay intact unless the delta explicitly says otherwise.

You can create a new capability spec when a delta exists but the main spec does not. The sync process generates the new specification file in the canonical specs directory to house the delta changes.

The best way to apply OpenSpec changes without archiving the branch is to sync the selected delta into the main specs, which intelligently merges the modifications while preserving unaffected documented behavior.

Handling renamed requirements during an OpenSpec sync involves detecting the rename action in the delta spec and applying it to the main specification set without losing the existing material tied to that requirement.

Syncing OpenSpec delta changes requires reading YAML-based spec files. The system processes these structured requirement files from both the change branch and the main specification directory to execute the merge.