skills.rest
8007342
8007342COMMUNITY
Explore all skills by this author →
GitHub

openspec-sync-specs

Merge delta spec changes into main OpenSpec capability specifications.

5|Updated Mar 21, 2026
Search Tags:#requirements#cli#merge#spec-driven development#openspec#spec sync#delta specs
One-click install
npx skills add https://github.com/8007342/tillandsias --skill openspec-sync-specs-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/8007342/tillandsias/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/8007342/tillandsias --skill openspec-sync-specs-8007342

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 while preserving existing content the delta does not mention. - Store-Aware Operation: Supports registered OpenSpec stores via --store <id> so specs in standalone repos can be synced too. - Safe Capability Retirement: Deletes a capability's spec.md only when strict conditions hold, and validates the result with openspec validate --specs. - Use Case: After drafting a change that adds scenarios to the user-auth capability, run the sync to update openspec/specs/user-auth/spec.md while keeping the change active for implementation. ## Quick Start Ask the agent to sync the delta specs from change "add-user-auth" into the main specs without archiving the 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 into main specs with OpenSpec?▼

Select the change, then the Skill reads each delta spec listed in artifactPaths.specs.existingOutputPaths and merges its ADDED, MODIFIED, REMOVED, and RENAMED requirements into the matching main spec. It finishes by running openspec validate --specs.

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

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

Does openspec sync-specs work with registered stores?▼

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

Can I sync only some delta specs from a change?▼

Yes. Name explicit entries from existingOutputPaths and only those paths are synced; the rest stay untouched. A named path not in the list is reported and the sync stops rather than silently dropping it.

When does the sync delete a capability's spec.md file?▼

Only when removing requirements leaves no requirement blocks, the spec is otherwise well-formed, the change declares retire_capabilities: true, and the file resolves inside the real specs root. Otherwise the sync stops and reports the blocking condition.

Related Skills

Explore More Software Engineering Skills→
MetaCubeXMetaCubeX
4.1k

openspec-sync-specs

Merge delta specifications into main specs under openspec/specs.

Official
Intermediate
linaproailinaproai
147

openspec-archive-change

Archive completed OpenSpec workflow changes to dated directories with completion validation.

Official
Intermediate
ducthang-hubducthang-hub

openspec-archive-change-ai-kit

Archives completed OpenSpec changes after validating artifacts and tasks, optionally syncing specs before moving to timestamped location.

Community
Advanced
leeoveryleeovery
27

start-feature

Generate a feature specification markdown file from inline context.

Community
Basic