skills.rest
NEETROF
NEETROFOFFICIAL
Explore all skills by this author →
GitHub

openspec-sync-specs

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

4|Updated Jun 21, 2026
Search Tags:#requirements#cli#spec-driven development#openspec#merging#spec sync#delta specs
One-click install
npx skills add https://github.com/NEETROF/cymbra --skill openspec-sync-specs-neetrof
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/NEETROF/cymbra/tree/main/.cursor/skills/openspec-sync-specs
Command: npx skills add https://github.com/NEETROF/cymbra --skill openspec-sync-specs-neetrof

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. - Change Selection: Lists available changes via the openspec CLI and prompts the user to pick one, never guessing. - Spec Creation: Creates new main spec files with Purpose and Requirements sections when a capability does not exist yet. - Use Case: After drafting a change proposal with delta specs for a new authentication feature, run this Skill to merge those requirements into the main specs while keeping the change active for implementation. ## 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 main spec files.

What is the delta spec format in OpenSpec?▼

Delta specs use markdown sections: ADDED Requirements for new requirements, MODIFIED Requirements for changes to existing ones, REMOVED Requirements for deletions, and RENAMED Requirements using FROM:/TO: pairs. Requirements contain scenarios with WHEN/THEN clauses.

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, keeping the proposal available for continued work.

What happens if the main spec file does not exist 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→
DataCoveyDataCovey
27

openspec-sync-specs

Merge delta specs from openspec/changes into main specs with intelligent merging.

Official
Advanced
mrclrchtrmrclrchtr
54

openspec-archive-change

Archive completed OpenSpec changes into date-prefixed directories with artifact validation.

Community
Advanced
YuDefineYuDefine
45

spectra-verify

Verify alignment between delta specs and code artifacts in change workflows.

Official
Advanced
accidental-hedge-fundaccidental-hedge-fund
3

openspec-sync-specs

Syncs changed fields from Delta specs to openspec master files.

Official
Intermediate