openspec-sync-specs

To merge delta spec changes intelligently, you can apply adds, modifies, removes, and renames from change branches into main specs while preserving unrelated content. This ensures scenarios are appended or updated without losing existing edits.

Automating openspec requirements updates involves reading delta specs and applying changes to canonical specification files. This process handles requirement additions, modifications, deletions, and renames while requiring user selection and confirmation for audit.

Intelligent merging handles removed requirements by deleting them from main specs and processes renamed requirements by updating their entries. It also adds new requirements and appends or updates scenarios for modified ones, preserving unrelated content.

Yes, syncing delta specs can create new capability spec files when needed. It reads changes under openspec/changes and applies them to openspec/specs, generating a clear summary of added, modified, removed, or renamed requirements for review.

Yes, delta discovery and selection prompts you to choose a specific change to apply from the available options under openspec/changes. This ensures user confirmation before merging delta specifications into the main spec files.

Syncing delta specs prevents inconsistent requirement states by automating the application of incremental edits into canonical files. This avoids manual errors, lost edits, and ensures all adds, modifies, removes, and renames are accurately reflected.