openspec-sync-specs

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

25|3|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/AkaraChen/2code --skill openspec-sync-specs-akarachen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/AkaraChen/2code/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/AkaraChen/2code --skill openspec-sync-specs-akarachen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Core Features & Use Cases

  • Intelligent delta merging: reads delta specs and applies changes to main specs with ADD/MODIFIED/REMOVED/RENAMED semantics.
  • Safe, guided updates: prompts for change names when missing and preserves existing content not mentioned in the delta.
  • Idempotent operations: running again yields the same final main specs.

Quick Start

Provide a delta change name when prompted and let the tool merge it into the main specs with intelligent, delta-driven updates.

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 losing existing content?

You can merge delta specs into main specs by applying ADDED, MODIFIED, REMOVED, and RENAMED changes. The tool uses intelligent merging to preserve existing content not mentioned in the delta workspace.

What is the best way to apply changes from a delta spec to main specifications?

Applying changes from a delta spec requires merging them into the main specs using intelligent, delta-driven updates. This process supports ADD, MODIFIED, REMOVED, and RENAMED semantics to safely update the main specifications.

Do I need the openspec CLI to sync delta specifications to main specs?

Yes, syncing delta specifications requires the openspec CLI. The tool operates over the openspec/changes delta workspace and main specs, and it will prompt for a change name when one is missing.

Can I run delta spec merging multiple times without duplicating changes?

Yes, merging delta specs is an idempotent operation. Running the tool again yields the same final main specs without duplicating changes or altering previously merged content.

When should I use delta spec merging instead of archiving a change?

Use delta spec merging when you want to update main specs with changes from a delta spec without archiving the change. This keeps the change active in the delta workspace while applying its modifications to the main specs.

Why does merging delta specs prompt for a change name?

Merging delta specs prompts for a change name when it is missing to correctly identify which delta workspace to read from. This ensures the tool applies the correct set of changes to the main specs.