openspec-sync-specs

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

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/Joao-Camilo-Mallmann/ofurry-motion-graphics --skill openspec-sync-specs-joao-camilo-mallmann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/Joao-Camilo-Mallmann/ofurry-motion-graphics/tree/main/.agents/skills/openspec-sync-specs
Command: npx skills add https://github.com/Joao-Camilo-Mallmann/ofurry-motion-graphics --skill openspec-sync-specs-joao-camilo-mallmann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specs 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 specs, with intelligent merging instead of wholesale copying. ## Core Features & Use Cases - Intelligent Delta Merging: Reads delta spec sections and applies partial updates, such as adding a single scenario without copying existing ones. - Change Selection Workflow: Lists available changes via the openspec CLI and prompts the user to select one when no change name is given. - New Capability Creation: Creates a new main spec file with Purpose and Requirements sections when a capability does not exist yet. - Use Case: After finishing a change proposal that adds two requirements and modifies one scenario, run the sync to update openspec/specs while keeping the change active for later archiving. ## Quick Start Ask the assistant to sync the delta specs from a specific OpenSpec change into the main specs without archiving it.

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 workflow with a change name, or let it list available changes with openspec list --json so you can pick one. It reads each delta spec and applies ADDED, MODIFIED, REMOVED, and RENAMED sections to the corresponding main spec files.

Does syncing specs archive the change in OpenSpec?

No, syncing updates main specs while the change remains active. You archive the change separately once implementation is complete, which keeps the proposal history available until then.

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

Include only the new scenario under a MODIFIED Requirements section in the delta spec. The merge treats deltas as intent, so existing scenarios and content not mentioned in the delta are preserved.

What happens if the capability has no main spec yet?

A new 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.

Can I sync specs from a registered OpenSpec store?

Yes, run openspec store list --json to find registered store ids, then pass --store <id> on commands that read or write specs and changes. Commands without a store flag act on the nearest local openspec directory.