openspec-sync-specs

Merge delta specs into main specs with idempotent updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specification changes often need to be propagated into the canonical main specs without creating duplicates or archiving changes. This skill automates that intelligent merge process.

Core Features & Use Cases

  • Intelligent delta-to-main spec synchronization: apply added, modified, removed, and renamed requirements while preserving existing content.
  • Delta-driven updates: read delta specs under openspec/changes/<name>/specs/*/spec.md and update or create corresponding main specs.
  • Safe, idempotent operation: repeated runs converge to the same main specs with minimal manual intervention.

Quick Start

Provide the delta change name and run the openspec sync command to merge delta specs 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 merge delta specs into main specs without archiving the changes?

To merge delta specs into main specs, read delta files from openspec/changes and apply added, modified, removed, or renamed requirements to update or create corresponding main specs while preserving existing unmentioned content.

What is the best way to apply delta specification changes to canonical main specs safely?

The best way to apply delta specification changes safely is using an automated, idempotent merge process that propagates updates into canonical main specs without creating duplicates or archiving the original delta changes.

How does idempotent spec synchronization work for openspec delta files?

Idempotent spec synchronization works by ensuring repeated merge runs converge to the same main specs, applying delta file updates with minimal manual intervention and without duplicating existing specification content.

Can I update modified and renamed requirements in main specs without losing existing content?

Yes, you can update modified and renamed requirements while preserving existing content, because the merge process only applies changes explicitly mentioned in the delta specs and leaves unmentioned canonical content untouched.

What file path format does openspec use for reading delta specs to sync?

The sync process reads delta specs from the openspec/changes/<name>/specs/*/spec.md file path structure to locate and extract the requirement changes needed for updating the main specifications.