openspec-sync-specs

To merge delta specs safely, this workflow reads delta files and applies them incrementally to main specs. It preserves existing content while handling ADDED, MODIFIED, REMOVED, and RENAMED sections to evolve your specifications accurately.

An idempotent merge means applying the same delta spec multiple times yields the same final main spec. This workflow ensures idempotent merging to prevent duplicate content or conflicting updates during repeated sync operations.

When delta specs contain ambiguous changes, this workflow includes guardrails that prompt for clarification before proceeding. It ensures safe partial updates by verifying intent rather than guessing the desired modification.

Yes, the workflow applies when a corresponding main spec is present or can be created. If a delta spec exists under openspec/changes and no main spec is found, it generates the new main spec automatically.

The best way to sync without archiving is running a delta-merge workflow. It intelligently reads delta specs and applies them to main specs, enabling updates to main specs while keeping the original delta intact.

Delta specs handle renamed sections through change-aware merging logic. The workflow detects RENAMED sections and applies them to main specs incrementally, ensuring structural integrity without duplicating the moved content.