openspec-sync-specs

Merging delta specs into main specs is done by reading changes from openspec/changes and applying added, modified, removed, and renamed requirements to openspec/specs while preserving existing content. The process uses intelligent merging rules to prevent wholesale replacements.

Delta spec management uses interactive prompts for ambiguous changes to ensure correct intent is captured before updating main spec files. This guided workflow prevents incorrect merges when applying delta modifications to primary specifications.

Running spec sync operations multiple times yields idempotent updates, meaning repeated runs do not recreate edits or duplicate changes. The process ensures delta specs are applied cleanly to openspec/specs and provides a clear summary of the final state.

Auto-creating or updating main spec files when capabilities are new or missing is supported during a delta merge. The tool reads the delta spec structure from openspec/changes and generates the corresponding primary specs automatically.

Applying renamed requirements from delta specs is handled by specific intelligent merging rules that update openspec/specs without dropping the requirement history. The tool processes these structural changes alongside added, modified, and removed requirements.

Reconciling delta specs with primary specifications is needed when delta specs drift from main specs, creating reconciliation overhead. This process updates the primary specs to reflect the latest delta changes while preserving existing content.