openspec-sync-specs

Merge delta specifications into main openspec specs without archiving deltas.

30|6|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/tatargabor/wt-tools --skill openspec-sync-specs-tatargabor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/tatargabor/wt-tools/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/tatargabor/wt-tools --skill openspec-sync-specs-tatargabor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta-to-main spec synchronization to apply intelligent changes without archiving the delta.

Core Features & Use Cases

  • Intelligent merging of ADDED, MODIFIED, REMOVED, and RENAMED requirements from delta specs into main specs.
  • Preservation of unrelated content; create missing main specs when needed.
  • Generates a clear summary of updates for audit and traceability.

Quick Start

Trigger the skill to merge pending delta specs into the main specification repository and update affected specs accordingly.

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 archiving the delta files?

To merge delta specs without archiving, apply intelligent synchronization to integrate ADDED, MODIFIED, REMOVED, and RENAMED requirements from openspec/changes into openspec/specs while preserving the original delta files.

What is delta-to-main spec synchronization in openspec?

Delta-to-main spec synchronization is the process of merging pending requirement changes from delta specs into the main repository, preserving unrelated content and generating an audit summary of updated capabilities.

How to apply modified and removed requirements from delta specifications to existing main specs?

Apply modified and removed requirements by reading both delta and main specifications, executing an intelligent merge that updates affected sections, and outputting a summary of all changed capabilities for traceability.

Can I sync delta specs if the corresponding main spec does not exist yet?

Yes, delta synchronization can create missing main specs automatically when needed, ensuring new capabilities defined in delta files under openspec/changes are properly established in openspec/specs.

Does merging delta specs preserve unrelated content in the main specifications?

Yes, intelligent merging preserves unrelated content in main specs, ensuring only the targeted ADDED, MODIFIED, REMOVED, and RENAMED requirements are updated while existing untouched sections remain intact.

What is the best way to track applied requirement changes after syncing delta specs?

The best way to track applied changes is through the generated summary of updated capabilities, which provides clear audit and traceability records after the delta-to-main spec merge completes.