openspec-sync-specs

Merging delta specs into main specs happens by reading changes from openspec/changes and applying them to the corresponding main spec. The process handles ADDED, MODIFIED, REMOVED, and RENAMED sections while preserving existing content.

A delta spec captures incremental changes that live in openspec/changes and must be propagated to main specs. You need to sync delta specs when updating capabilities to prevent drift and avoid manual rework across your documentation.

Applying openspec changes across multiple capabilities involves running a sync command with a targeted change name. The workflow reads the delta spec and updates corresponding main spec files, supporting various delta sections to keep all specs aligned.

Spec merging is both idempotent and safe. Re-running the process does not alter stable data, and it preserves content not mentioned in the delta, ensuring your existing main spec files remain intact during updates.

When clarification is needed during merging, the workflow prompts for input before proceeding. This ensures changes are applied accurately to the main spec files and prevents incorrect modifications.

Automating openspec documentation updates without manual rework is possible through agent-driven merging. The workflow automatically reads delta specs and updates main specs, supporting typical delta sections to keep specs aligned.