openspec-sync-specs

Merge delta specs into main specs with auditable, idempotent updates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/terry90918/horse-blessing-2026 --skill openspec-sync-specs-terry90918
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/terry90918/horse-blessing-2026/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/terry90918/horse-blessing-2026 --skill openspec-sync-specs-terry90918

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often diverge from main specs, making merges error-prone and hard to audit. This skill provides a safe, agent-driven workflow to apply changes from delta specs directly into the main specs without archiving the delta.

Core Features & Use Cases

  • Intelligent merging of delta and main specs, handling ADDED, MODIFIED, REMOVED, and RENAMED requirements while preserving existing content.
  • Non-destructive, idempotent updates with an auditable summary of changes for traceability.
  • Auto-create main specs for new capabilities and initialize them with the added requirements when needed.

Quick Start

Provide the delta spec name and run the synchronization process to merge it 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 archiving the changes?

To merge delta specs into main specs, this skill applies changes directly from openspec/changes into openspec/specs without archiving, preserving unrelated content while handling ADDED, MODIFIED, REMOVED, and RENAMED requirements.

What is the best way to apply delta spec changes while preserving unrelated main spec content?

Intelligent merging applies targeted modifications to main specs while leaving existing unrelated sections untouched, ensuring non-destructive, idempotent updates with an auditable summary of changes.

Can I auto-create main specs when a delta spec introduces a completely new capability?

Yes, the skill auto-creates missing main spec files in openspec/specs and initializes them with the added requirements from the delta spec when a new capability is introduced.

Does the spec merge process provide an auditable summary of updates?

Yes, the merge process provides an auditable summary of updates ensuring traceability, while guaranteeing idempotent execution so repeated runs do not duplicate modifications.

How do I handle RENAMED and REMOVED requirements when syncing openspec delta specs?

The skill intelligently processes RENAMED and REMOVED requirements from delta specs to update or delete corresponding entries in main specs while maintaining overall document integrity.