openspec-sync-specs

Merge delta spec requirements into main OpenSpec specification files.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill openspec-sync-specs-pavelvdo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/openspec-sync-specs
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill openspec-sync-specs-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After implementing a change, delta specs in an OpenSpec change folder must be reflected in the main specs; doing this by hand is error-prone and tedious. This Skill applies ADDED, MODIFIED, REMOVED, and RENAMED requirement sections from delta specs to the main spec files with intelligent partial merging, without archiving the change. ## Core Features & Use Cases - Intelligent requirement merging: Adds new requirements, applies partial scenario updates, removes deprecated requirements, and renames requirements while preserving untouched content. - Change selection workflow: Infers the change from context, auto-selects when only one active change exists, or prompts the user to pick from changes that contain delta specs. - Report generation: Writes a sync report to openspec/changes/<name>/reports/spec-sync-<name>-YYYY-MM-DD.md and keeps chat output to a single summary line. - Use Case: After finishing implementation of a change, run the sync so openspec/specs/<capability>/spec.md reflects the delta, then proceed to /opsx:verify or /opsx:archive. ## Quick Start Ask the assistant to sync the delta specs of the current change into the main specs, optionally naming the change explicitly.

Frequently Asked Questions about openspec-sync-specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync delta specs to main specs in OpenSpec?

Invoke the sync operation with an optional change name; the agent reads each delta spec under openspec/changes/<name>/specs and applies ADDED, MODIFIED, REMOVED, and RENAMED sections to openspec/specs/<capability>/spec.md. The change itself is not archived.

How does OpenSpec handle partial requirement updates?

MODIFIED sections support partial updates: you can add a single new scenario without copying existing ones. The agent merges the delta intent into the main spec while preserving scenarios and content not mentioned in the delta.

Does syncing specs require the openspec CLI?

Yes, the skill declares compatibility with the openspec CLI, which is used to list active changes when the change name cannot be inferred from context. The actual spec edits are performed by the agent reading and writing markdown files.

What happens if no delta specs are found for a change?

The operation stops with a single chat line stating that no delta spec was found and suggesting next steps such as archiving the change or continuing the proposal. No main spec files are modified.

Is the spec sync operation idempotent?

Yes, running the sync twice produces the same result. If the main specs already match the delta, no files change and the chat output reports that specs are already synchronized.