skills.rest
ValorVie
ValorVieCOMMUNITY
Explore all skills by this author →
GitHub

openspec-sync-specs

Sync delta specs from an OpenSpec change into main specs without archiving the change.

Updated Jan 5, 2025
Search Tags:#documentation#requirements#merge#spec-driven development#openspec#spec sync#delta specs
One-click install
npx skills add https://github.com/ValorVie/settingZsh --skill openspec-sync-specs-valorvie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/ValorVie/settingZsh/tree/main/.gemini/skills/openspec-sync-specs
Command: npx skills add https://github.com/ValorVie/settingZsh --skill openspec-sync-specs-valorvie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specifications aligned with in-progress 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 to the main specs, with intelligent partial merging instead of wholesale replacement. ## Core Features & Use Cases - Delta-driven spec updates: Reads delta spec files under openspec/changes/<name>/specs/ and applies each section to the corresponding main spec. - Intelligent merging: Adds single scenarios to existing requirements, updates descriptions, removes deprecated requirements, and renames requirements while preserving untouched content. - New capability creation: Creates a new main spec file with Purpose and Requirements sections when a capability does not exist yet. - Use Case: After drafting a change proposal for a new API capability, sync its delta specs into the main specs so the canonical documentation reflects the planned behavior while the change stays active for implementation. ## Quick Start Ask the assistant to sync the delta specs from a specific OpenSpec change into the main specs, or let it list available changes so you can pick one.

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

Run the sync operation with a change name, or let the assistant list available changes via `openspec list --json` so you can select one. It reads each delta spec under openspec/changes/<name>/specs and applies the changes to openspec/specs.

What delta spec sections does OpenSpec support?▼

Delta specs support ADDED, MODIFIED, REMOVED, and RENAMED requirement sections. MODIFIED sections can contain only the new or changed scenarios, since the merge preserves existing content not mentioned in the delta.

Does syncing specs archive the OpenSpec change?▼

No, syncing only updates the main specs and leaves the change active. You archive the change separately once its implementation is complete.

What happens if the main spec for a capability does not exist?▼

A new main spec file is created at openspec/specs/<capability>/spec.md with a Purpose section (which can be marked TBD) and a Requirements section containing the ADDED requirements from the delta.

Is the OpenSpec sync operation idempotent?▼

Yes, the operation is designed to be idempotent, so running it twice produces the same result. Existing requirements are updated in place rather than duplicated.

Related Skills

Explore More Software Engineering Skills→
ValorVieValorVie

openspec-sync-specs

Sync delta specs from an OpenSpec change into main specs without archiving the change.

Community
Intermediate
studyzystudyzy
10.3k

openspec-archive-change

Archives completed OpenSpec changes after verifying artifact and task completion.

Community
Intermediate
UnterrainerInformatikUnterrainerInformatik

openspec-sync-specs

Sync delta specs from an OpenSpec change into main specification files.

Official
Intermediate
accidental-hedge-fundaccidental-hedge-fund
3

openspec-sync-specs

Syncs changed fields from Delta specs to openspec master files.

Official
Intermediate