openspec-sync-specs

Merging delta specs into main specs safely involves applying only the intended changes while preserving existing content. This synchronization reads delta specifications, validates the changes, and outputs a merged main spec with an active change set.

Synchronizing delta specifications in an openspec workflow is done by reading delta specs located under openspec/changes and applying them to openspec/specs. This change-set driven process ensures updates are merged intelligently without archiving the original changes.

Yes, delta spec merges are designed with safeguards and idempotence, ensuring repeated runs yield the exact same result. This prevents duplicate entries and preserves any main spec content not explicitly mentioned in the delta specifications.

You need to provide a change name for the merge process to identify the correct delta specs. If the change name is missing, the synchronization process will prompt you for clarification before applying the updates to the main specs.

A key limitation is that merging only applies intended changes from delta specs while explicitly preserving existing content not mentioned in the delta. You must ensure your delta specs accurately validate changes before synchronization to avoid unintended omissions.