openspec-sync-specs

Merge delta specifications into main OpenSpec specs with intelligent changes.

4|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/finger-gun/sisu --skill openspec-sync-specs-finger-gun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/finger-gun/sisu/tree/main/.kilocode/skills/openspec-sync-specs
Command: npx skills add https://github.com/finger-gun/sisu --skill openspec-sync-specs-finger-gun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specifications into the main specs safely and incrementally, eliminating manual overwrites and the risk of losing changes during merges.

Core Features & Use Cases

  • Intelligent delta merging: applies ADDED, MODIFIED, REMOVED, and RENAMED changes to main specs while preserving untouched content.
  • Delta discovery and guidance: reads delta specs from openspec/changes/<name>/specs and guides user choices when the change is ambiguous.
  • Automatic spec creation: creates missing main spec files and scaffolds the initial Requirements section when needed.
  • Guardrails and prompts: prompts for user input on ambiguous changes to ensure intentional updates.

Quick Start

Run the openspec-sync-specs tool to merge delta changes into main specs by specifying the delta change name and following the prompts.

Frequently Asked Questions about openspec-sync-specs

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

FAQPage Schema
How do I safely merge delta specs into main specs without overwriting content?

Merging delta specs safely requires applying changes intelligently instead of wholesale replacements. This tool reads delta files and updates main specs incrementally, preserving untouched content while prompting for input on ambiguous modifications to prevent data loss.

How does delta specification synchronization work with ambiguous changes?

Delta specification synchronization works by enforcing guardrails and prompting for user input when changes are ambiguous. This ensures all updates to main specs are intentional and prevents accidental overwrites during the merge process.

Do I need the openspec CLI to sync delta specifications into main specs?

Yes, the openspec CLI is required to execute the sync process. The tool reads delta specifications from the openspec/changes directory and merges them into main specs under openspec/specs, creating new files and scaffolding sections when needed.

What happens when a main spec file is missing during a delta merge?

When a main spec file is missing during a delta merge, the sync tool automatically creates it and scaffolds the initial Requirements section. This ensures new specifications are properly structured before applying the delta changes.

Can I sync RENAMED changes in delta specifications to update main specs?

Yes, you can sync RENAMED changes alongside ADDED, MODIFIED, and REMOVED operations. The tool applies all these delta change types to update main specs accurately while preserving existing content not mentioned in the delta.