skills.rest
mosakuzii0216
mosakuzii0216COMMUNITY
Explore all skills by this author →
GitHub

openspec-sync-specs

Merge delta spec changes into main OpenSpec capability specifications.

Updated Jul 1, 2025
Search Tags:#requirements#cli#merge#spec-driven development#openspec#spec sync#delta specs
One-click install
npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill openspec-sync-specs-mosakuzii0216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/mosakuzii0216/mosaku-v1/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill openspec-sync-specs-mosakuzii0216

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. - Change Selection & Validation: Resolves the target change via openspec status, validates the result with openspec validate --specs, and supports store-scoped operations with --store <id>. - Capability Lifecycle Handling: Creates new main specs for new capabilities and safely retires capabilities by deleting emptied spec files when retirement conditions are met. - Use Case: After finishing 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 continued work. ## Quick Start Ask the assistant to sync the delta specs from a named OpenSpec change 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 OpenSpec delta specs into main specs?▼

Select the change by name or let it be inferred from context, then the delta specs listed in the status JSON are merged into the corresponding main specs under the specs root. The change stays active afterward and can be archived later.

What is the difference between openspec sync and openspec archive?▼

Sync updates the main specs with delta changes while keeping the change active for further work. Archive performs a similar merge but also closes out the change once implementation is complete.

Does the sync work with OpenSpec stores?▼

Yes. Run openspec store list --json to discover registered 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.

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

Yes. A caller can narrow the sync to an explicit subset of paths from artifactPaths.specs.existingOutputPaths. Only the named paths are synced and the remaining delta specs are left untouched.

When does syncing delete a main spec file?▼

A spec.md is deleted 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
zabinyzabiny
2

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta-spec status.

Official
Advanced
blueraaiblueraai

skill-activation

Manage Bluera Knowledge skill auto-activation settings via JSON configuration files.

Official
Basic