openspec-sync-specs

Merge delta spec changes into main OpenSpec capability specifications.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-sync-specs-raphaelmans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/raphaelmans/spectralpointengineering/tree/main/.skillshare/skills/openspec-sync-specs
Command: npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-sync-specs-raphaelmans

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 specs, without archiving the change. ## Core Features & Use Cases - Intelligent Merging: Reads each delta spec and merges requirements into main specs while preserving existing scenarios and content the delta does not mention. - Store-Aware Operation: Supports registered OpenSpec stores via --store <id> so specs in standalone repositories can be synced from anywhere. - Safe Capability Retirement: Deletes a capability's spec.md only when strict conditions hold (empty requirements, valid Purpose, retire_capabilities: true marker), and validates results with openspec validate --specs. - Use Case: After finishing a change that adds scenarios to the user-auth capability, run the sync to update openspec/specs/user-auth/spec.md in place while keeping the change active for continued work. ## Quick Start Ask the assistant to sync the delta specs from a named change into the main specs, for example: sync the specs from my add-billing-invoices change 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 infer the change from context. It reads delta specs from the change's artifactPaths.specs.existingOutputPaths, merges them into main specs under the planning root, then validates with openspec validate --specs.

How do I update main specs without archiving an OpenSpec change?

Use this sync operation instead of openspec archive. It applies the same intelligent merge of ADDED, MODIFIED, REMOVED, and RENAMED requirements into main specs while leaving the change active for further work.

Can I sync specs from an OpenSpec store outside my repository?

Yes. Run openspec store list --json to find registered store ids, then pass --store <id> on the status, instructions, and validate commands. The store flag stays sticky for the whole workflow and main spec paths resolve inside the store.

When does syncing delete a capability spec file?

A spec.md is deleted only when the sync removes all requirement blocks, the spec remains well-formed with a Purpose, the change declares retire_capabilities: true, and the file resolves inside the real specs root. Otherwise the sync stops and reports the blocking condition.

What happens if a MODIFIED delta drops existing scenarios?

The merge preserves scenarios and content the delta does not mention. A MODIFIED block must carry the whole requirement including surviving scenarios, since openspec validate and openspec archive reject deltas that silently drop scenarios.