openspec-sync-specs

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

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/sanfordzhang/blockgame --skill openspec-sync-specs-sanfordzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/sanfordzhang/blockgame/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/sanfordzhang/blockgame --skill openspec-sync-specs-sanfordzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta spec updates can drift from the main specification; this Skill automates reading delta changes and applying them into the canonical specs, reducing manual merge effort and errors.

Core Features & Use Cases

  • Intelligent merging of delta specs into main specs, preserving unrelated content.
  • Handles ADDED, MODIFIED, REMOVED, and RENAMED changes with idempotent application.
  • Creates main spec files when a capability does not exist yet, and generates a concise summary of changes.

Quick Start

Run the OpenSpec CLI to merge delta specs into the main specifications.

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?

To merge delta specs into main specs, the Skill reads delta changes and applies them into canonical specs intelligently, preserving unrelated content. It handles ADDED, MODIFIED, REMOVED, and RENAMED changes with idempotent application.

What is the best way to apply delta changes to canonical specifications?

Applying delta changes to canonical specifications is best handled by automated merging, which reads delta specs and applies changes directly without archiving. This approach reduces manual merge effort and errors while generating a concise summary of changes.

How does change management handle delta spec updates that drift from main specifications?

Change management for drifting delta spec updates works by reading delta changes and applying them into the main specifications. This automated process prevents drift and ensures the canonical specs reflect the latest updates without manual intervention.

Can I create main spec files automatically when a capability does not exist yet?

Yes, you can create main spec files automatically when a capability does not exist. The Skill detects missing canonical specs during the merge process and creates the necessary main spec files to apply the delta changes successfully.

Does OpenSpec CLI support idempotent application of REMOVED and RENAMED changes?

Yes, OpenSpec CLI supports idempotent application of REMOVED and RENAMED changes. It processes these delta changes alongside ADDED and MODIFIED operations to ensure merging delta specs into main specs yields consistent results.

What are the limitations of merging delta specs without archiving?

Merging delta specs without archiving applies changes directly to main specs, meaning the original pre-merge state is not preserved. This approach focuses on updating canonical specifications and generating a summary report rather than maintaining historical delta records.