openspec-sync-specs

Merge delta spec changes into main OpenSpec specification files.

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

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 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. - Store-Aware Operation: Discovers registered OpenSpec stores via the CLI and targets the correct specs root for every read and write. - Guardrailed Workflow: Uses only the delta paths reported by openspec status, honors caller-narrowed subsets, and validates artifact rules before any main-spec write. - Use Case: After drafting a change with delta specs for a billing capability, ask the agent to sync those deltas into the main specs so the canonical documentation reflects the new requirements while the change stays active. ## Quick Start Ask the agent to sync the delta specs from a named OpenSpec change into the main specs, for example by saying: sync the specs from the add-billing 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 into main specs with OpenSpec?▼

Invoke this Skill with a change name, or let it infer the change from context. It reads the delta specs listed by openspec status, then intelligently merges ADDED, MODIFIED, REMOVED, and RENAMED requirements into the main spec files.

What is the difference between syncing specs and archiving a change?▼

Syncing updates the main specs while keeping the change active for further work. Archiving also syncs the deltas but then closes and archives the change, marking it complete.

Does openspec-sync-specs work with registered OpenSpec stores?▼

Yes. When a store is named, the Skill runs openspec store list to discover store ids and passes the --store flag to commands, so main specs are read and written in the store's root rather than the local repository.

Can I sync only some delta specs instead of all of them?▼

Yes. You can name an explicit subset of delta spec paths, and only those will be merged. The Skill never widens a narrowed selection back to the full list and reports named paths that do not exist.

What happens if a change has no delta specs to sync?▼

The Skill checks artifactPaths.specs.existingOutputPaths from the status JSON. If it is empty or missing, it reports that there are no delta specs to sync and stops without writing any main spec.