openspec-sync-specs

Merge delta spec changes into main OpenSpec specifications without archiving.

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

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, with intelligent partial merging instead of wholesale file replacement. ## Core Features & Use Cases - Intelligent Requirement Merging: Applies ADDED, MODIFIED, REMOVED, and RENAMED requirement sections from delta specs while preserving existing scenarios and content not mentioned in the delta. - Store-Aware Operation: Discovers registered OpenSpec stores via openspec store list --json and targets the correct specs root for every read and write. - New Capability Spec Creation: Creates a new main spec with a Purpose section and Requirements section when a capability does not exist yet. - Use Case: After finishing a change that adds a billing scenario to an existing requirement, run the sync to update the main billing spec with just that scenario while leaving 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 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 to main specs in OpenSpec?

Run the sync workflow with a change name, or let it infer the change from context. It reads delta spec paths from the status JSON, then merges ADDED, MODIFIED, REMOVED, and RENAMED requirements into the main specs under the planning root.

Does syncing specs archive the change in OpenSpec?

No, syncing updates the main specs while the change remains active. You archive the change separately once implementation is complete, which is the key difference from the archive workflow.

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

Yes, you can name an explicit subset of delta spec paths to sync, and only those are merged. The named paths must exist in the status JSON output paths; unknown paths are reported and skipped rather than silently dropped.

What happens if a MODIFIED requirement only adds one scenario?

The merge is partial and intelligent: the new scenario is added to the existing requirement without copying or replacing existing scenarios. Content not mentioned in the delta is preserved, and the operation is idempotent.

Why does spec sync fail before writing any main spec?

Sync stops if the specs-instruction command exits non-zero or returns invalid JSON, since artifact rules may constrain the output format. It also stops when no delta specs exist in the status output rather than inferring paths from other artifacts.