skills.rest
alexei-lexx
alexei-lexxCOMMUNITY
Explore all skills by this author →
GitHub

openspec-sync-specs

Merge delta specifications into canonical main spec files.

Updated Jun 4, 2025
Search Tags:#automation#workflow#documentation#openspec#spec-sync#delta-merge
One-click install
npx skills add https://github.com/alexei-lexx/budget --skill openspec-sync-specs-alexei-lexx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/alexei-lexx/budget/tree/main/.gemini/skills/openspec-sync-specs
Command: npx skills add https://github.com/alexei-lexx/budget --skill openspec-sync-specs-alexei-lexx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta spec synchronization to main specs. This tool ensures controlled merging of delta changes into the canonical spec set, preserving provenance and reducing conflicts.

Core Features & Use Cases

  • Intelligent merging: Applies ADDED, MODIFIED, REMOVED, and RENAMED changes to main specs without wholesale replacements, preserving existing scenarios.
  • Interactive change selection: Prompts the user to select which delta changes to apply, preventing accidental merges.
  • Automated spec updates: Reads both delta and main specs, updates or creates main spec files, and provides a clear summary of changes.

Quick Start

Run the openspec-sync-specs tool to merge all pending delta specs into their corresponding 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 specifications into main specs without losing existing scenarios?▼

To merge delta specs into main specs without losing existing scenarios, use an intelligent delta-merge tool that applies ADDED, MODIFIED, REMOVED, and RENAMED changes. This preserves unrelated content and updates canonical spec files safely.

What is delta spec synchronization and when do I need it?▼

Delta spec synchronization applies targeted changes from delta specifications into a canonical main spec set. You need it when updating software documentation to ensure controlled merging, preserve provenance, and reduce manual conflicts.

Can I select which delta changes to apply during spec synchronization?▼

Yes, you can select which delta changes to apply during spec synchronization. Interactive change selection prompts allow you to review and choose specific ADDED, MODIFIED, REMOVED, or RENAMED sections, preventing accidental merges.

Does merging modified spec sections overwrite the entire main spec file?▼

No, merging modified spec sections does not overwrite the entire main spec file. Intelligent merging applies targeted changes to specified capabilities while preserving existing scenarios and unrelated content within the canonical main spec files.

What's the best way to automate workflow updates for renamed spec capabilities?▼

The best way to automate workflow updates for renamed spec capabilities is using a spec synchronization tool that processes RENAMED sections. It reads delta and main specs, updates files interactively, and reports a summary of applied changes.

Why does my delta spec merge fail to preserve unrelated content in main specs?▼

Delta spec merges fail to preserve unrelated content when using wholesale file replacements instead of intelligent merging. A proper delta-merge applies only ADDED, MODIFIED, REMOVED, and RENAMED sections to specified capabilities, preserving existing scenarios.

Related Skills

Explore More Software Engineering Skills→
remiverdiesenremiverdiesen
6

openspec-sync-specs

Merge delta specification changes into main spec files with an idempotent summary.

Community
Intermediate
caelaxiecaelaxie

openspec-sync-specs

Merge delta specification changes into main markdown spec files.

Community
Intermediate
RheasilviaRheasilvia

design-md

Lint DESIGN.md files and export design tokens to Tailwind or DTCG formats.

Community
Intermediate
unicorn-pluginsunicorn-plugins
21

resolve-conflict

Resolve discrepancies between specification files and source code.

Official
Advanced