openspec-sync-specs

Merge delta spec blocks into main OpenSpec spec files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill merges delta specs into main OpenSpec specs by applying delta changes to the primary spec files, ensuring consistency and version control.

Core Features & Use Cases

  • Delta-to-main merging: Reads delta specs and updates corresponding main specs, creating new ones when missing.
  • Intelligent merging: Preserves unchanged content and applies delta changes with an explicit intent, supporting added, modified, or renamed items.
  • Use Case: When a delta spec introduces a change to a capability, this skill merges it into the main spec so the main specs stay up-to-date with changes.

Quick Start

Run the openspec-sync-specs command to begin merging delta specs into main specs and follow prompts if multiple delta options exist.

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 OpenSpec specs?

To merge delta specs into main OpenSpec specs, scan openspec/changes/<change-name>/specs for delta blocks and apply changes to openspec/specs/<capability>/spec.md. The operation updates existing files or creates new ones while preserving unrelated content.

What is delta-spec merging in OpenSpec?

Delta-spec merging in OpenSpec is the process of reading delta changes from openspec/changes/ and applying them to primary spec files. It ensures main specs stay up-to-date by adding, modifying, or renaming items with explicit intent.

Does OpenSpec spec merging preserve unchanged content in main spec files?

Yes, OpenSpec spec merging preserves unchanged content. It intelligently applies only the delta changes to the primary spec files, ensuring unrelated sections remain untouched while updating or creating the targeted spec.md files.

Can I run OpenSpec delta merging multiple times without duplicating changes?

Yes, you can run delta merging multiple times safely because the operation is idempotent. Repeated execution of the openspec-sync-specs command applies the same delta changes without creating duplicate entries or corrupting the main spec files.

What happens when delta intent is ambiguous during spec merging?

When delta intent is ambiguous during spec merging, the process pauses and prompts for clarification. This ensures changes are applied with explicit intent, preventing incorrect modifications to the main OpenSpec spec files.

Are there any dependencies required to sync OpenSpec delta specs?

No external dependencies are required to sync OpenSpec delta specs. The operation works directly within the openspec/ directory structure to scan delta blocks and update main spec files without needing additional tools or libraries.