skills.rest
zh-impact
zh-impactCOMMUNITY
Explore all skills by this author →
GitHub

openspec-sync-specs

Sync delta specs from OpenSpec changes into main specification files.

Updated Apr 7, 2026
Search Tags:#markdown#requirements#cli#spec-driven development#openspec#spec sync#delta specs
One-click install
npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-sync-specs-zh-impact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/zh-impact/agent-feeder/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-sync-specs-zh-impact

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 to the main spec files, without archiving the change. ## Core Features & Use Cases - Intelligent Merging: Applies partial updates such as adding a single scenario to an existing requirement without copying unchanged content. - Delta Spec Parsing: Reads delta spec files under openspec/changes/<name>/specs/ and interprets ADDED, MODIFIED, REMOVED, and RENAMED sections. - New Spec Creation: Creates a new main spec file when a capability does not yet exist in openspec/specs/. - Use Case: After drafting a change proposal with delta specs, run this Skill to update the main specs so they reflect the intended behavior while the change remains 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 for you to 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 this Skill and optionally provide a change name. It reads delta spec files under openspec/changes/<name>/specs/, applies ADDED, MODIFIED, REMOVED, and RENAMED sections to the main specs, and shows a summary of what changed.

What is a delta spec in OpenSpec?▼

A delta spec is a markdown file under a change's specs directory describing intended changes to a capability. It uses sections like ADDED Requirements, MODIFIED Requirements, REMOVED Requirements, and RENAMED Requirements to express the difference from the main spec.

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 implementation is complete, so the change remains available for tracking during development.

Can I add a single scenario without rewriting the whole requirement?▼

Yes, the sync performs intelligent merging. Including only the new scenario under MODIFIED Requirements adds it to the main spec while preserving existing scenarios and content not mentioned in the delta.

What happens if the capability has no main spec yet?▼

The Skill creates a new main spec file at openspec/specs/<capability>/spec.md with a Purpose section and the ADDED requirements from the delta spec. The Purpose can be brief or marked as TBD.

Related Skills

Explore More Software Engineering Skills→
MetaCubeXMetaCubeX
4.1k

openspec-sync-specs

Merge delta specifications into main specs under openspec/specs.

Official
Intermediate
studyzystudyzy
10.3k

openspec-archive-change

Archives completed OpenSpec changes after verifying artifact and task completion.

Community
Intermediate
CybernetKZCybernetKZ

tz-review

Reviews OpenSpec change proposals against codebase facts before implementation.

Official
Advanced
joannanowakowskajoannanowakowska

openspec-sync-specs

Merge delta specifications into canonical OpenSpec files with requirement-level updates.

Community
Advanced