openspec-sync-specs

Sync delta specs from an OpenSpec change into main specification files.

6|7|Updated Jun 4, 2026
One-click install
npx skills add https://github.com/nodesource/nsolid-plugin --skill openspec-sync-specs-nodesource
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/nodesource/nsolid-plugin/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/nodesource/nsolid-plugin --skill openspec-sync-specs-nodesource

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specifications aligned 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 to the main spec files, with intelligent merging instead of wholesale replacement. ## Core Features & Use Cases - Intelligent Delta Merging: Reads delta specs and applies partial updates to main specs, preserving existing scenarios and content not mentioned in the delta. - Change Selection Workflow: Lists available changes via the openspec CLI and prompts the user to select one, avoiding guesswork. - New Capability Creation: Creates new main spec files with Purpose and Requirements sections when a capability does not exist yet. - Use Case: After drafting a change proposal with delta specs for a new API feature, run this Skill to merge those requirements into the main specs while keeping the change active until implementation is archived. ## Quick Start Ask the assistant to sync the delta specs from a specific 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 delta specs to main specs in OpenSpec?▼

Run the sync operation with a change name, or let the assistant list available changes with openspec list --json so you can select one. It reads each delta spec and applies ADDED, MODIFIED, REMOVED, and RENAMED requirements to the corresponding main spec files.

How does OpenSpec delta spec merging work?▼

Merging is agent-driven rather than programmatic. The assistant reads both the delta spec and the main spec, then applies partial updates such as adding a single scenario under MODIFIED without copying existing scenarios, preserving all content not mentioned in the delta.

Does syncing specs archive the OpenSpec change?▼

No, syncing only updates the main specs and leaves the change active. You archive the change separately once implementation is complete, which keeps the proposal history available until then.

What happens if the capability has no main spec yet?▼

A new main spec file is created at openspec/specs/<capability>/spec.md with a brief Purpose section (marked TBD if needed) and a Requirements section containing the ADDED requirements from the delta spec.

Why does spec sync stop in workspace-planning mode?▼

When openspec status reports actionContext.mode as workspace-planning, workspace spec sync is not supported in that slice. The operation stops explicitly instead of falling back to repo-local paths or editing linked repositories.