skills.rest
hongwt
hongwtCOMMUNITY
Explore all skills by this author →
GitHub

openspec-sync-specs

Merge delta spec changes into main OpenSpec capability specifications.

Updated Jun 28, 2026
Search Tags:#requirements#cli#merge#spec-driven development#openspec#spec sync#delta specs
One-click install
npx skills add https://github.com/hongwt/dsplm-monitor --skill openspec-sync-specs-hongwt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/hongwt/dsplm-monitor/tree/main/.pi/skills/openspec-sync-specs
Command: npx skills add https://github.com/hongwt/dsplm-monitor --skill openspec-sync-specs-hongwt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specifications in sync with change proposals is tedious and error-prone when done by hand. This Skill applies delta specs (ADDED, MODIFIED, REMOVED, RENAMED requirements) from an OpenSpec change directly into the main specs, without archiving the change. ## Core Features & Use Cases - Intelligent Merging: Reads each delta spec and merges requirements into main specs, preserving existing scenarios and content the delta does not mention. - Change Selection & Store Support: Infers the change from context, lists active changes when ambiguous, and supports registered OpenSpec stores via --store <id>. - Validation & Safe Retirement: Runs openspec validate --specs after syncing and only deletes a retired capability's spec file when strict conditions are met. - Use Case: After finishing a change that adds scenarios to the user-auth capability, ask the agent to sync the delta specs so the main spec reflects the new requirements while the change stays active. ## Quick Start Ask the agent to sync the delta specs from a named change into the main specs, for example: sync the specs from the add-user-auth change.

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?▼

Provide a change name or let the agent infer it from context. The skill reads the delta specs listed in the change status, merges their requirements into the main specs under the planning root, and validates the result with openspec validate.

How to update main specs without archiving an OpenSpec change?▼

Use this sync workflow instead of openspec archive. It applies the delta spec changes to the main specs while leaving the change active, so you can archive later once implementation is complete.

Does openspec sync work with registered stores?▼

Yes. Run openspec store list --json to discover store ids, then pass --store <id> on commands that read or write specs and changes. The flag stays sticky for the rest of the workflow.

What happens when a requirement is removed in a delta spec?▼

The requirement block is removed from the main spec. The entire spec file is only deleted when strict retirement conditions hold, including a retire_capabilities marker in the change's .openspec.yaml and no remaining requirement blocks.

Why does spec sync stop before writing a main spec?▼

Sync stops if the specs-instruction lookup fails or returns invalid JSON, if no delta specs exist in the change status, or if a caller-named path is not in the existing output paths. It reports the blocking condition instead of writing.

Related Skills

Explore More Software Engineering Skills→
MetaCubeXMetaCubeX
4.1k

openspec-sync-specs

Merge delta specifications into main specs under openspec/specs.

Official
Intermediate
captaincontratcaptaincontrat

openspec-archive-change

Archives completed OpenSpec changes with metadata preservation using the openspec CLI.

Official
Advanced
runtime-envruntime-env
47

openspec-sync-specs

Merge delta specifications into main specifications under openspec/specs.

Official
Intermediate
Gentleman-ProgrammingGentleman-Programming
1.3k

sdd-archive

Merge delta specs into main specs and archive completed changes.

Official
Advanced