openspec-sync-specs

To merge delta specs into main specs safely, the skill reads both files first, applies added, modified, removed, and renamed requirements intelligently, and preserves unrelated content during the update.

A delta spec captures incremental changes beside main OpenSpec specs. You need to merge it when applying proposed capability changes across multiple spec files to ensure the primary specs reflect the latest updates.

Yes, delta merging supports broad scenarios by applying changes across multiple capabilities and delta directories under openspec/changes/<name>/specs, resolving all modifications in a single idempotent update flow.

The merge handles modified requirements by prompting for user selection when necessary, reading both delta and main specs beforehand to ensure safe, idempotent updates without wholesale replacement of content.

The best way to automate spec updates is providing the delta change name to trigger the merge flow, which safely resolves renamed and removed requirements while applying idempotent updates to the main specs.

When merging renamed or removed requirements, the operation requires reading both delta and main specs beforehand and may prompt for user selection to ensure safe updates, preventing wholesale replacement of existing content.