openspec-sync-specs

Merging delta specs into main specs safely requires applying ADDED, MODIFIED, REMOVED, and RENAMED changes while preserving content not mentioned in the delta. This process avoids wholesale replacements and ensures the original intent remains intact.

When no main specs exist during a delta spec merge, the process automatically creates new main specs from the provided delta changes. This ensures the openspec workflow initializes correctly without manual file scaffolding.

Handling ambiguous delta details during main spec updates involves prompting the user for clarification before applying changes. This prevents incorrect modifications and ensures the merged specifications accurately reflect the intended delta requirements.

Yes, the delta spec merge process is idempotent for repeated workflow automation runs. Applying the same delta spec multiple times yields the same final main spec state without duplicating entries or corrupting the existing structure.

The best way to automate applying REMOVED and RENAMED changes to openspec files is using an intelligent merge tool that reads the delta and main specs directly. It safely applies structural updates and summarizes changes after each run.

You need a delta change name to trigger the merge, but you do not need existing main specs. The process reads delta specs from the changes directory and creates new main specs in the specs directory when none are present.