openspec-sync-specs

You can merge delta specs into main specs automatically by providing a delta change name to an agent, which then reads the delta files and applies ADDED, MODIFIED, REMOVED, and RENAMED changes to update the main specs.

When syncing delta specs, existing content not mentioned in the delta is preserved. The operation only applies the specified changes and prompts for missing context when change names are ambiguous.

Yes, you can auto-create missing main spec files during a delta merge. The agent will create the new files and document their purpose and requirements as needed.

Agent-driven workflows handle ambiguous delta spec changes by guarding the operation and prompting the user for change names when the context is missing, ensuring consistent application without guessing.

You need to merge delta specs to prevent drift and reduce manual merge overhead. Keeping them separate causes inconsistencies, while merging ensures changes are applied consistently without archiving the delta.

Yes, merging delta specs supports multiple capabilities at once. The process reads the delta and main specs, applying the required changes across various capabilities simultaneously.