openspec-sync-specs

To merge delta specs into main specs, the tool reads delta changes under openspec/changes and applies ADDED, MODIFIED, REMOVED, and RENAMED requirements to the corresponding main specification files. It preserves existing content and creates missing main specs on demand.

Synchronizing requirements without losing existing content is achieved through intelligent delta-driven merging, which applies only the specified changes from delta specs while preserving all unrelated content in the main specification files.

Delta-to-main spec synchronization handles renamed requirements by reading the RENAMED delta changes and applying them directly to the corresponding main specification files, ensuring the requirements stay current without manual edits.

Yes, you can automatically create missing main specs when applying delta changes. The merging process creates the necessary main specification files on demand if they do not already exist in the target directory.

The limitations of automated spec merging include its strict operation on delta sets located specifically under openspec/changes/<name>/specs, meaning it cannot process requirements outside this delta structure or handle unsupported change types.