skills.rest
ValorVie
ValorVieCOMMUNITY
Explore all skills by this author →
GitHub

openspec-sync-specs

Merge delta specs into main specification files with idempotent updates.

5|1|Updated Jan 14, 2026
Search Tags:#automation#merge#idempotent#openspec#cli-tool#delta-specs#spec-management
One-click install
npx skills add https://github.com/ValorVie/custom-skills --skill openspec-sync-specs-valorvie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/ValorVie/custom-skills/tree/main/project-template/.gemini/skills/openspec-sync-specs
Command: npx skills add https://github.com/ValorVie/custom-skills --skill openspec-sync-specs-valorvie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges delta specs into main specs by applying delta changes to main specification files.

Core Features & Use Cases

  • Delta-spec driven merging: reads delta specs and updates corresponding main specs.
  • Intelligent, idempotent updates: adds new requirements, updates existing ones, and preserves unrelated content.
  • Automatic main-spec creation and summary: creates missing main specs when needed and reports changes.

Quick Start

Provide a delta spec and run the openspec-sync-specs tool to merge changes 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 idempotently?▼

Delta spec merging works by reading delta specs from openspec/changes and applying changes to corresponding files in openspec/specs. It interprets ADDED, MODIFIED, REMOVED, and RENAMED sections to intelligently update requirements while preserving unrelated content.

What happens to unrelated content when merging delta specs into main specifications?▼

Unrelated content is preserved during delta spec merging. The merge process only applies changes defined in ADDED, MODIFIED, REMOVED, and RENAMED sections, leaving existing main spec content that is not referenced by the delta completely untouched.

How to create missing main specs automatically from delta specs?▼

Missing main specs are created automatically when a delta spec references a specification file that does not yet exist in openspec/specs. The merge process initializes the new main spec and applies the delta changes, finishing with a clear summary of what was created.

Can I use openspec-sync-specs to apply REMOVED and RENAMED sections in delta specs?▼

Yes, openspec-sync-specs interprets REMOVED and RENAMED sections within delta specs. It processes these changes alongside ADDED and MODIFIED sections to update main specs accordingly, ensuring the final specification files reflect the intended structural changes.

Do I need a specific directory structure to merge openspec delta changes?▼

You need openspec/changes for delta specs and openspec/specs for main specs. The merge tool operates across these two directories to read pending changes and apply them to the corresponding main specification files.

Related Skills

Explore More Software Engineering Skills→
CloudDevCrusaderCloudDevCrusader
1

openspec-sync-specs

Merge delta specification changes into main specification documents.

Community
Advanced
psaccpsacc

openspec-sync-specs

Merge delta specification changes into main openspec spec files.

Community
Advanced
yun-s-ohyun-s-oh

openspec-sync-specs

Synchronizes delta specifications into main specifications using the openspec CLI.

Community
Intermediate
cenmiaocenmiao

openspec-sync-specs

Merge delta spec changes into main specification files.

Community
Advanced