openspec-sync-specs

Sync delta specs from an OpenSpec change into main specs without archiving.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill openspec-sync-specs-te-quanbzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/TE-QuanBZhang/skills-pool/tree/main/ai-coding/skills/openspec-sync-specs
Command: npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill openspec-sync-specs-te-quanbzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specifications aligned with in-progress 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 specs, with intelligent partial merging instead of wholesale replacement. ## Core Features & Use Cases - Intelligent Delta Merging: Reads delta specs and applies only the stated changes to main specs, preserving existing scenarios and content not mentioned in the delta. - CodeGraph-Grounded Updates: Explores the codebase with CodeGraph before editing so spec changes align with actual code symbols and architecture. - Interactive Change Selection: Lists available changes via openspec list --json and prompts the user to pick one, never guessing or auto-selecting. - Use Case: A developer finished drafting a change with delta specs for two capabilities but is not ready to archive it. They run this Skill to update openspec/specs/<capability>/spec.md files in place while the change remains active. ## Quick Start Ask the AI 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 OpenSpec delta specs to main specs?

Run this Skill with a change name, or let it list available changes via openspec list --json and prompt you to select one. It reads each delta spec and applies ADDED, MODIFIED, REMOVED, and RENAMED requirements to the corresponding main spec files.

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

Syncing updates main specs with delta changes while keeping the change active for further work. Archiving finalizes the change after implementation is complete. Use sync when you want main specs updated mid-development without closing the change.

Does OpenSpec spec sync require the OpenSpec CLI?

Yes, the Skill requires the openspec CLI to list changes and resolve change status via openspec status --change <name> --json. It also uses CodeGraph to explore codebase context before applying spec edits.

Can I add a single scenario to a requirement without copying the whole requirement?

Yes, the delta format supports partial updates. Include only the new scenario under MODIFIED Requirements, and the merge preserves all existing scenarios and content not mentioned in the delta.

What happens if I run the spec sync twice on the same change?

The operation is designed to be idempotent, so running it twice produces the same result. Existing requirements matching ADDED entries are treated as implicit modifications rather than duplicated.

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 Skill stops explicitly rather than falling back to repo-local paths or editing linked repositories.