openspec-sync-specs

Merge delta specifications into main spec files while preserving unrelated content.

11|3|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/DarkHighness/coi-public --skill openspec-sync-specs-darkhighness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/DarkHighness/coi-public/tree/main/.gemini/skills/openspec-sync-specs
Command: npx skills add https://github.com/DarkHighness/coi-public --skill openspec-sync-specs-darkhighness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes delta-spec updates and applies them to main specs, enabling intelligent merging and preventing wholesale rewrites.

Core Features & Use Cases

  • Agent-driven delta merging: read delta specs and modify corresponding main specs.
  • Content-preserving edits: apply ADDED/MODIFIED/REMOVED/RENAMED blocks while keeping unrelated content intact.
  • Lifecycle management: create main spec files when missing and report a concise change summary.

Quick Start

Provide the delta change name to synchronize; I will apply it to the main specs and report the results.

Frequently Asked Questions about openspec-sync-specs

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

FAQPage Schema
How do I automate syncing delta specs into main specs without rewriting entire files?

Delta spec syncing applies intelligent merges to update main specs by processing ADDED, MODIFIED, REMOVED, and RENAMED blocks, preserving all unrelated content within the original specification files.

What is the best way to apply delta specs organized under openspec/changes to main specifications?

Applying delta specs from openspec/changes/<name>/specs/* automatically updates or creates the corresponding openspec/specs/<capability>/spec.md file, intelligently merging changes while preventing wholesale rewrites of your main specs.

Can I create main spec files automatically when they are missing during a delta merge?

Yes, delta spec synchronization creates main spec files automatically when missing, intelligently applying your ADDED, MODIFIED, REMOVED, and RENAMED blocks to populate the new openspec/specs/<capability>/spec.md file.

How do I handle RENAMED and REMOVED blocks when merging delta specifications?

Merging delta specifications respects RENAMED and REMOVED blocks by applying targeted edits to main specs, ensuring only the specified changes are synchronized while keeping all unrelated specification content intact.

Does delta spec syncing preserve unrelated content when updating main specs?

Yes, delta spec synchronization preserves unrelated content by applying intelligent merges that only target the specified ADDED, MODIFIED, REMOVED, and RENAMED blocks, preventing wholesale rewrites of the main specification.

How do I get a summary of changes after synchronizing delta specs into main specs?

After synchronizing delta specs into main specs, the process returns a concise summary of changes detailing exactly how the ADDED, MODIFIED, REMOVED, and RENAMED blocks updated the corresponding main specification files.