openspec-sync-specs

Merge delta spec changes into main OpenSpec capability specifications.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/creevey/rprtr --skill openspec-sync-specs-creevey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/creevey/rprtr/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/creevey/rprtr --skill openspec-sync-specs-creevey

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, without archiving the change. ## Core Features & Use Cases - Intelligent Merging: Applies delta requirements into main specs while preserving existing scenarios and content the delta does not mention. - Change Selection & Validation: Resolves the target change via openspec status and openspec list, then validates updated specs with openspec validate --specs. - Capability Retirement: Safely deletes a retired capability's spec.md only when strict conditions hold, including the retire_capabilities: true marker. - Use Case: After finishing a change that adds a billing requirement, ask the agent to sync the delta specs so the main specs reflect the new requirement while the change stays active for implementation. ## Quick Start Ask the agent to sync the delta specs from your 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?

Invoke this Skill with an optional change name; it reads the delta specs listed in the change's artifactPaths.specs.existingOutputPaths and merges their ADDED, MODIFIED, REMOVED, and RENAMED requirements into the corresponding main specs, then runs openspec validate --specs.

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

Syncing updates the main specs from a change's delta specs while leaving the change active for continued implementation. Archiving also applies the deltas but then closes and archives the change, so sync is used when work is still in progress.

Does openspec-sync-specs require the openspec CLI?

Yes, the Skill requires the openspec CLI to be installed. It runs commands such as openspec status, openspec list, openspec instructions specs, and openspec validate to resolve changes, fetch rules, and verify the merged specs.

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

Yes, a caller can narrow the sync by naming explicit entries from existingOutputPaths, and only those delta specs are merged. The Skill never widens a narrowed selection back to the full list and reports named paths that are not found.

When does the sync delete a retired capability's spec file?

The spec.md is deleted only when removing requirements leaves no 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.