openspec-sync-specs

Merge delta spec changes into main OpenSpec capability specifications.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/neuthos/ldx-monorepo --skill openspec-sync-specs-neuthos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/neuthos/ldx-monorepo/tree/main/.agents/skills/openspec-sync-specs
Command: npx skills add https://github.com/neuthos/ldx-monorepo --skill openspec-sync-specs-neuthos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main capability 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 with intelligent merging, without archiving the change. ## Core Features & Use Cases - Intelligent Requirement Merging: Applies ADDED, MODIFIED, REMOVED, and RENAMED requirement blocks from delta specs while preserving untouched scenarios and content in main specs. - Store-Aware Operation: Discovers registered OpenSpec stores via openspec store list --json and scopes all reads and writes with --store <id> when a store is selected. - Safe Capability Retirement: Deletes a retired capability's spec.md only when strict conditions hold, including the retire_capabilities: true marker, and reports blocking conditions otherwise. - Use Case: After finishing a change that adds scenarios to the user-auth spec, run the sync to update specs/user-auth/spec.md in place, validate with openspec validate --specs, and keep the change active until implementation is complete. ## Quick Start Sync the delta specs from my current 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?▼

Select the change, run openspec status --change "<name>" --json to get delta spec paths from artifactPaths.specs.existingOutputPaths, then merge each delta into the matching main spec under the planning root. Finish by running openspec validate --specs to confirm the result.

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

Use the sync-specs workflow instead of openspec archive. It applies the delta requirements to main specs directly while leaving the change active, so you can archive later once implementation is complete.

Does openspec sync work with registered stores?▼

Yes. Run openspec store list --json to discover store ids, then pass --store <id> on commands like status, list, show, and validate. The flag stays sticky for the whole workflow and the planning root resolves to the store.

When is a capability spec.md deleted during sync?▼

A spec.md is deleted only when removing requirements leaves no requirement blocks, the spec is otherwise 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 requirement drops existing scenarios?▼

A MODIFIED block must carry the whole requirement including every surviving scenario, because openspec validate and openspec archive reject deltas that drop scenarios the main spec still has. Content not mentioned in the delta is preserved in place.