openspec-sync-specs

Merge delta spec changes into main OpenSpec specification files.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill openspec-sync-specs-jonathanlin768
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/jonathanlin768/CS2Match-Nakama/tree/main/.agents/skills/openspec-sync-specs
Command: npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill openspec-sync-specs-jonathanlin768

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 to the main spec files, without archiving the change. ## Core Features & Use Cases - Intelligent Merging: Applies partial updates such as adding a single scenario to an existing requirement without copying unchanged content. - CLI-Driven Context: Uses openspec list and openspec status --json to resolve the change and locate delta spec files. - New Capability Creation: Creates openspec/specs/<capability>/spec.md with Purpose and Requirements sections when the capability does not exist yet. - Use Case: After drafting a change proposal with delta specs, ask the agent to sync them so the main specs reflect the new requirements while the change stays active for implementation. ## Quick Start Ask the agent to sync the delta specs from a specific OpenSpec change into the main specs, for example by saying: sync the specs from my add-login-flow 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 to main specs?

Provide a change name, or let the agent list available changes with openspec list --json and prompt you to select one. The agent reads each delta spec and applies ADDED, MODIFIED, REMOVED, and RENAMED requirements to the main spec files.

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

Syncing updates the main specs with the delta content while keeping the change active for ongoing implementation. Archiving is a separate step performed after implementation is complete.

Does syncing specs require the openspec CLI?

Yes, the openspec CLI is required. The workflow runs openspec list --json to enumerate changes and openspec status --change <name> --json to resolve delta spec file paths.

Can I sync only part of a requirement, like adding one scenario?

Yes, the merge is intelligent and partial. A MODIFIED requirement containing only a new scenario adds that scenario to the main spec without copying or altering existing scenarios.

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

The agent creates 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 agent stops and does not fall back to repo-local paths or edit linked repositories.