openspec-sync-specs

Name: openspec-sync-specs
Availability: InStock
Author: rozx

Merge delta specs into primary specs while preserving existing content.

25|4|Updated Nov 13, 2025

Search Tags:#automation #workflow #integration #merge #openspec #delta-specs #spec-management

Ready to run

npx skills add https://github.com/rozx/Tsukuyomi --skill openspec-sync-specs-rozx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/rozx/Tsukuyomi/tree/main/.opencode/skills/openspec-sync-specs
Command: npx skills add https://github.com/rozx/Tsukuyomi --skill openspec-sync-specs-rozx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often drift from main specs, creating reconciliation overhead. This Skill provides a guided, idempotent workflow to read delta specs and apply their changes to the primary specifications while preserving existing content.

Core Features & Use Cases

Intelligent merging of ADDED, MODIFIED, REMOVED, and RENAMED requirements from delta specs into main specs without wholesale replacements
Interactive prompts for ambiguous changes to ensure correct intent is captured
Idempotent updates with a clear summary, so repeated runs do not recreate edits
Auto-create or update main spec files when capabilities are new or missing
Supports delta spec structure like openspec/changes/<name>/specs/<capability>/spec.md

Quick Start

Use the openspec-sync-specs tool to merge delta specs into the 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 specs into main specs without losing existing content?▼

Merging delta specs into main specs is done by reading changes from openspec/changes and applying added, modified, removed, and renamed requirements to openspec/specs while preserving existing content. The process uses intelligent merging rules to prevent wholesale replacements.

How does delta spec management handle ambiguous requirement changes?▼

Delta spec management uses interactive prompts for ambiguous changes to ensure correct intent is captured before updating main spec files. This guided workflow prevents incorrect merges when applying delta modifications to primary specifications.

What happens when I run spec sync operations multiple times on the same files?▼

Running spec sync operations multiple times yields idempotent updates, meaning repeated runs do not recreate edits or duplicate changes. The process ensures delta specs are applied cleanly to openspec/specs and provides a clear summary of the final state.

Can I auto-create main spec files for new capabilities during a delta merge?▼

Auto-creating or updating main spec files when capabilities are new or missing is supported during a delta merge. The tool reads the delta spec structure from openspec/changes and generates the corresponding primary specs automatically.

What is the best way to apply renamed requirements from delta specs into primary specs?▼

Applying renamed requirements from delta specs is handled by specific intelligent merging rules that update openspec/specs without dropping the requirement history. The tool processes these structural changes alongside added, modified, and removed requirements.

When do I need to reconcile delta specs with primary specifications?▼

Reconciling delta specs with primary specifications is needed when delta specs drift from main specs, creating reconciliation overhead. This process updates the primary specs to reflect the latest delta changes while preserving existing content.