openspec-sync-specs

To merge delta specs into main specs without losing content, this tool applies changes intelligently by adding, modifying, removing, or renaming requirements while preserving existing content. It safely integrates delta spec changes without copying the entire requirement.

Syncing openspec delta specs involves reading delta files from openspec/changes and editing main specs directly. This agent-driven operation creates new spec files when needed and applies changes idempotently, ensuring merges are safe to re-run.

To apply ADDED, MODIFIED, REMOVED, or RENAMED operations to spec files, the tool reads delta specs and directly edits main specs. It processes these operations to apply changes exactly as described in the delta documentation.

Yes, you can safely re-run spec merges multiple times. The merging process is idempotent, preserving content not mentioned in the delta and ensuring repeated operations do not duplicate or corrupt existing main spec requirements.

If no change name is provided when syncing delta specs, the tool prompts for selection using openspec list --json and the AskUserQuestion tool. It also prompts for clarification during the merge process when needed.

Yes, merging openspec delta specs creates new main spec files when missing. It reads delta specs from openspec/changes and either applies changes to existing specs in openspec/specs or creates the required files.