skills.rest
33may
33mayCOMMUNITY
Explore all skills by this author →
GitHub

openspec-sync-specs

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

1|1|Updated Nov 28, 2025
Search Tags:#requirements#cli#spec-driven development#openspec#merging#spec sync#delta specs
One-click install
npx skills add https://github.com/33may/robotics --skill openspec-sync-specs-33may
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/33may/robotics/tree/main/humanoid/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/33may/robotics --skill openspec-sync-specs-33may

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specifications up to date with changes defined in delta specs is tedious and error-prone when done manually. This Skill applies ADDED, MODIFIED, REMOVED, and RENAMED requirements from a change's delta specs directly into 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. - Change Selection: Lists available changes via the openspec CLI and prompts the user to select one, never guessing or auto-selecting. - 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 with delta specs for a new API feature, run this Skill to merge those requirements into the main specs while keeping the change active until implementation is complete. ## Quick Start Ask the assistant to sync the delta specs from your current OpenSpec change into the main specs.

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 and prompt you to select one. It reads each delta spec and applies ADDED, MODIFIED, REMOVED, and RENAMED requirements to the corresponding main spec files.

How do I add a single scenario to an existing requirement in a spec?▼

Include only the new scenario under a MODIFIED Requirements section in the delta spec. The sync applies partial updates, adding that scenario without copying or altering existing scenarios in the main spec.

Does syncing specs archive the OpenSpec change?▼

No, syncing delta specs to main specs does not archive the change. The change remains active so you can archive it separately once implementation is complete.

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

The sync creates a new spec file 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 spec.

Why does spec sync stop in workspace-planning mode?▼

When openspec status reports actionContext.mode as workspace-planning, workspace spec sync is not supported in that slice. The operation stops explicitly rather than falling back to repo-local paths or editing linked repositories.

Related Skills

Explore More Software Engineering Skills→
UnterrainerInformatikUnterrainerInformatik

openspec-sync-specs

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

Official
Intermediate
CoderCoco-StudiosCoderCoco-Studios
1

openspec-archive-change

Archive completed OpenSpec changes after verifying artifacts, tasks, and spec synchronization.

Official
Advanced
firstsun-devfirstsun-dev
3

openspec-archive-change

Archive completed OpenSpec changes after verifying artifacts, tasks, and spec sync state.

Official
Advanced
joannanowakowskajoannanowakowska

openspec-sync-specs

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

Community
Advanced