openspec-sync-specs

Merge delta specifications into main specs with ADDED, MODIFIED, REMOVED, and RENAMED rules.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/johnqxu/skills --skill openspec-sync-specs-johnqxu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/johnqxu/skills/tree/main/dot_eprint_skills/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/johnqxu/skills --skill openspec-sync-specs-johnqxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs from a change to main specs and update main specs with delta changes, without archiving the change.

Core Features & Use Cases

  • Intelligent delta application across capabilities using ADDED, MODIFIED, REMOVED, and RENAMED rules.
  • On-demand main spec creation: create openspec/specs/<capability>/spec.md when a capability doesn't exist yet, preserving existing content.
  • Safe, guided workflow: prompts for change selection when multiple delta changes are available and preserves content not mentioned in the delta.

Quick Start

Provide a delta change name to merge delta specs into main specs, or let the tool prompt you to select one.

Frequently Asked Questions about openspec-sync-specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge delta specs into main specs without archiving the change?

You can sync delta specs by applying ADDED, MODIFIED, REMOVED, and RENAMED rules to existing main specs. This updates the main specs with delta changes while preserving the original change without archiving it.

What happens to existing content when applying delta specifications to main specs?

When applying delta specifications, existing content not mentioned in the delta is preserved. The merge is idempotent, ensuring repeated applications do not overwrite or duplicate unaffected main spec content.

Can I create a new main spec automatically if the capability does not exist?

Yes, missing main specs are created on demand. When a capability does not exist, the tool generates the openspec/specs/<capability>/spec.md file while preserving existing content during the delta merge.

How does change management handle ambiguous delta changes during spec merges?

When a change name is ambiguous, the tool prompts you to select the correct delta change. This guided workflow ensures the intended delta specifications are applied to the appropriate main specs safely.

Does openspec spec management support idempotent merges for change workflows?

Yes, openspec spec management ensures idempotent merges across change workflows. Applying the same delta specs multiple times yields identical main spec results without duplicating requirements or losing data.