openspec-sync-specs

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

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/thewoolleyman/personal-knowledge-base --skill openspec-sync-specs-thewoolleyman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/thewoolleyman/personal-knowledge-base/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/thewoolleyman/personal-knowledge-base --skill openspec-sync-specs-thewoolleyman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping main specifications up to date with changes defined in OpenSpec delta specs requires tedious manual merging, and naive copying can overwrite existing requirements or scenarios that should be preserved. ## Core Features & Use Cases - Intelligent Delta Merging: Applies ADDED, MODIFIED, REMOVED, and RENAMED requirement sections from delta specs into main specs while preserving untouched content. - Interactive Change Selection: Lists available changes via openspec list --json and prompts the user to select one instead of guessing. - New Spec Creation: Creates a new main spec file with Purpose and Requirements sections when a capability does not exist yet. - Use Case: After drafting a change with delta specs for a new API capability, run this Skill to merge those requirements into the main specs without archiving the change, keeping the change active until implementation is complete. ## Quick Start Ask the assistant to sync the delta specs from a specific OpenSpec change into the main specs.

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?▼

Run this Skill and optionally provide a change name. It reads delta specs under openspec/changes/<name>/specs, applies ADDED, MODIFIED, REMOVED, and RENAMED sections to the matching main specs, and shows a summary of what changed.

What is the difference between syncing and archiving an OpenSpec change?▼

Syncing updates the main specs with the delta changes while keeping the change active for continued work. Archiving is a separate step performed after implementation is complete, which this Skill deliberately does not do.

Does syncing delta specs overwrite existing scenarios in main specs?▼

No. The merge is intelligent and partial: MODIFIED requirements only apply the scenarios or description changes stated in the delta, and all existing content not mentioned in the delta is preserved.

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

The Skill creates a new spec file at openspec/specs/<capability>/spec.md with a brief Purpose section (marked TBD) and a Requirements section containing the ADDED requirements from the delta spec.

What tools are required to run the OpenSpec sync workflow?▼

The openspec CLI must be installed, since the Skill runs openspec list --json to discover available changes. The actual merging is agent-driven by reading and editing the spec Markdown files directly.