openspec-sync-specs

To merge delta specs into main specs without losing existing content, use a synchronization tool that applies ADDED, MODIFIED, and RENAMED directives from your delta directory to the core specifications. This process updates or creates main specs while preserving untouched content during the merge operation.

A delta specification contains incremental changes meant to update core specifications. You need to sync delta specs when changes live alongside main specs and must be applied to the core without archiving or duplicating work, ensuring the main specifications reflect the latest modifications coherently.

Applying ADDED and MODIFIED directives involves reading delta specs from the changes directory and intelligently merging them into the main OpenSpec specifications. This updates the core specs by adding new content or altering existing sections, producing a coherent main specification with minimal disruption to the structure.

Yes, you can re-run delta spec synchronization without causing duplicates because the operation is idempotent. Re-running yields the same outcome as long as the delta content remains unchanged, ensuring safe, repeatable merges into the main specifications without introducing redundant data or errors.

Yes, spec sync works with RENAMED directives in OpenSpec. The synchronization process intelligently applies ADDED, MODIFIED, and RENAMED directives to produce a coherent main spec, handling renames safely while applying changes from the delta to the core specifications with minimal disruption.

If your main spec does not update, ensure the delta file is correctly placed under the openspec/changes directory. The synchronization tool reads delta specs from this specific project structure and updates or creates main specs under openspec/specs according to the delta directives found there.