openspec-sync-specs

To merge delta specs without overwriting, apply ADDED, MODIFIED, REMOVED, and RENAMED changes intelligently from the delta files to preserve existing main spec content. This controlled merge process prevents wholesale overwrites by only applying specified changes.

An idempotent spec merge means applying the same delta specs multiple times yields the same final main specs without duplicating changes. This ensures consistent synchronization outcomes and prevents accidental content duplication during repeated updates.

Apply changes from openspec delta files by reading them from the openspec/changes directory and processing ADDED, MODIFIED, REMOVED, and RENAMED operations against the main specs, creating missing main spec files automatically if the capability does not exist.

Yes, you can automatically create a new main spec file if the capability does not exist yet. The merge process reads the delta spec and initializes the new main spec file with the specified ADDED content directly.

Yes, merging delta specs preserves content not mentioned in the change file. The synchronization process applies only the targeted modifications while leaving all other existing content in the main specs completely untouched.

The best way to synchronize openspec changes is to use an automated merge tool that reads delta specs, applies changes idempotently, creates missing files, and summarizes updates to keep main specifications current without manual intervention.