openspec-sync-specs

To merge delta specs into main specs automatically, provide a delta change name to apply, and the system will read both spec types, apply ADDED, MODIFIED, REMOVED, and RENAMED rules, and update the main specifications while preserving unrelated content. It also creates missing main specs when a capability is newly introduced, outputting a concise summary of changes for traceability.

Delta spec synchronization in OpenSpec workflows is the process of applying delta changes to existing capabilities to keep main specifications up to date without archiving the changes. It enables reproducible, auditable updates by applying specific rules like ADDED, MODIFIED, REMOVED, and RENAMED to merge changes safely into main specs.

Yes, merging delta specs preserves unrelated content in the main spec. The intelligent merging process specifically respects ADDED, MODIFIED, REMOVED, and RENAMED change rules, ensuring that only the targeted delta changes are applied while leaving all other existing content in the main specifications untouched.

Yes, you can automatically create missing main specs from a delta spec. When a capability is introduced by a delta spec and the corresponding main spec does not exist, the sync process automatically creates the missing main spec file to ensure the new capability is properly documented.

To review changes after syncing delta specs into main specs, you can read the concise summary of changes generated by the tool. This summary provides traceability and documents exactly what ADDED, MODIFIED, REMOVED, and RENAMED rules were applied to the main specifications during the merge.

The idempotent spec management process applies delta changes to existing capabilities but does not archive the original changes. It relies on ADDED, MODIFIED, REMOVED, and RENAMED rules to merge delta specs into main specs, meaning any changes outside these defined rules in the delta spec may not be synced into the main specification.