openspec-sync-specs

Merge delta specification changes into canonical main specs with idempotent updates.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/mazhewitt/budget-analyser --skill openspec-sync-specs-mazhewitt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/mazhewitt/budget-analyser/tree/main/.gemini/skills/openspec-sync-specs
Command: npx skills add https://github.com/mazhewitt/budget-analyser --skill openspec-sync-specs-mazhewitt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often diverge from the main specifications; this skill merges delta changes back into the canonical main specs to keep documentation consistent and up-to-date without archiving the delta.

Core Features & Use Cases

  • Intelligent delta merge: read delta specs and apply changes to main specs while preserving existing content.
  • Safe, idempotent updates: merge additions, modifications, removals, and renames without overwriting unrelated sections.
  • Use Case: a delta spec introduces a new scenario; the skill adds that scenario to the main spec without duplicating or overwriting other content.

Quick Start

Sync a delta spec into the main specs by selecting a delta change and applying it to the main specification set.

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 specifications into main specs without losing existing content?

Merging delta specs into main specs requires reading delta files and applying intelligent, idempotent updates that preserve existing content while applying ADDED, MODIFIED, REMOVED, and RENAMED changes across multiple capabilities.

What is the best way to sync OpenSpec delta changes to canonical specifications?

Syncing OpenSpec delta changes involves reading delta specs at openspec/changes and applying them directly to canonical main specs at openspec/specs, updating the main specification set without archiving the delta.

Does delta spec merging support idempotent updates for additions and removals?

Idempotent delta spec merging safely applies additions, modifications, removals, and renames to main specifications without overwriting unrelated sections or duplicating existing content during repeated sync operations.

How do I apply a new scenario from a delta spec to an existing capability specification?

Applying a new delta spec scenario uses intelligent merge logic to append the scenario to the main capability spec, ensuring the new content integrates without duplicating or overwriting existing specification sections.

Can I sync delta spec changes across multiple capabilities at once?

Syncing delta spec changes across multiple capabilities is supported by reading delta files and applying intelligent merges to each corresponding main spec, preserving existing content while propagating updates.

Why merge delta specs into main specs instead of archiving the delta?

Merging delta specs into main specs keeps canonical documentation consistent and up-to-date by applying changes directly, eliminating the divergence that occurs when delta files are simply archived separately.