openspec-sync-specs

Sync delta specs from OpenSpec changes into main specification files.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill openspec-sync-specs-marcel-carrillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/Marcel-Carrillo/ProyectosIA/tree/main/.cursor/skills/openspec-sync-specs
Command: npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill openspec-sync-specs-marcel-carrillo

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 specs, with intelligent merging instead of wholesale replacement. ## Core Features & Use Cases - Intelligent Delta Merging: Applies partial updates such as adding a single scenario to an existing requirement without copying unchanged content. - CLI-Driven Context Resolution: Uses openspec list and openspec status --json to discover changes and locate delta spec files, prompting the user when the change name is ambiguous. - New Capability Creation: Creates openspec/specs/<capability>/spec.md with Purpose and Requirements sections when a capability does not yet exist. - Use Case: After drafting a change proposal for a new checkout flow, run the sync to merge its delta requirements into the main specs while keeping the change active until implementation is archived. ## Quick Start Ask the assistant to sync the delta specs from a specific OpenSpec change into the main specs without archiving the 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 OpenSpec delta specs into main specs?▼

Provide a change name, or let the skill list available changes via `openspec list --json` and prompt you to select one. It then reads each delta spec and applies ADDED, MODIFIED, REMOVED, and RENAMED sections to the corresponding main spec files.

How to add a single scenario to an existing OpenSpec requirement?▼

Include only the new scenario under a MODIFIED Requirements section in the delta spec. The sync merges it into the existing requirement in the main spec while preserving all scenarios not mentioned in the delta.

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.

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

The sync creates a new spec file at openspec/specs/<capability>/spec.md with a brief Purpose section marked TBD and a Requirements section containing the ADDED requirements from the delta.

Why does spec sync stop with a workspace-planning message?▼

When `openspec status` reports actionContext.mode as workspace-planning, spec sync is not supported for that slice. The skill stops intentionally and does not fall back to repo-local paths or edit linked repositories.