openspec-sync-specs

Sync delta specs from OpenSpec changes into main specification files.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/twaananen/6dof-drone-sim --skill openspec-sync-specs-twaananen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/twaananen/6dof-drone-sim/tree/main/.agents/skills/openspec-sync-specs
Command: npx skills add https://github.com/twaananen/6dof-drone-sim --skill openspec-sync-specs-twaananen

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. - Full Delta Support: Handles ADDED, MODIFIED, REMOVED, and RENAMED requirement sections across multiple capability specs. - New Spec 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 with delta specs under openspec/changes/, ask the agent to sync them so the main specs in openspec/specs/ reflect the intended behavior while the change stays active. ## Quick Start Ask the agent to sync the delta specs from a specific OpenSpec change into the main specs, for example by saying: sync the specs from my add-user-auth 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 delta specs to main specs in OpenSpec?▼

Provide a change name, or let the agent list available changes with openspec list --json so you can pick one. The agent reads each delta spec under openspec/changes/<name>/specs/ and applies the ADDED, MODIFIED, REMOVED, and RENAMED sections to the matching main spec.

What is the delta spec format in OpenSpec?▼

Delta specs use markdown sections: ADDED Requirements for new requirements, MODIFIED Requirements for changes, REMOVED Requirements for deletions, and RENAMED Requirements with FROM/TO pairs. Requirements contain scenarios written with WHEN and 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 the implementation is complete.

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

Yes, the sync performs intelligent merging. Include only the new scenario under MODIFIED Requirements, and the agent adds it to the existing requirement while preserving all other scenarios and content.

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

The agent 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.