openspec-sync-specs

To sync delta spec changes into main spec files, run the skill with a delta change name to idempotently merge ADDED, MODIFIED, REMOVED, and RENAMED requirements while preserving unrelated content. It automatically updates or creates the corresponding main spec files under openspec/specs.

Merging incremental requirements without losing existing spec content is achieved through capability-scoped, idempotent delta merging. The process applies delta spec sections directly to main specs while preserving any main-spec content not mentioned in the delta.

Handling requirement versioning for a non-existent capability is done through capability-aware spec creation. The merge process creates a new main spec file for that capability and seeds it with the delta's added requirements.

Applying delta spec updates with a missing or ambiguous change name triggers interactive change selection. The skill prompts you to choose a specific change from the available openspec CLI changes before proceeding with the merge.

During a spec sync, removed or renamed requirements are applied to the main spec files alongside added and modified blocks. The process produces a clear summary of exactly what changed across the capability scope.

Automating OpenSpec requirement updates eliminates manual, error-prone editing of main requirement files. It ensures idempotent, capability-scoped merging of delta changes, preventing accidental data loss and maintaining spec consistency.