openspec-sync-specs

Merge delta spec changes into main OpenSpec specification files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual propagation of change-set delta specs into canonical OpenSpec main specs is error-prone and time consuming; this Skill automates reading, interpreting, and merging intent-based spec changes so teams avoid copy-paste mistakes and preserve existing content.

Core Features & Use Cases

  • User-guided change selection: Prompts the user to choose the specific change when the change name is not provided or ambiguous.
  • Intelligent merging: Applies ADDED, MODIFIED, REMOVED, and RENAMED sections from delta specs into main specs without overwriting unrelated scenarios.
  • Spec creation and summaries: Creates new capability spec files when needed, preserves untouched content, and produces a concise summary of applied edits for review.
  • Use Case: Product managers and spec maintainers can apply a delta authored in openspec/changes/<name>/specs to the main openspec/specs tree to add a feature, introduce new scenarios, or retire requirements with clear traceability.

Quick Start

Run the openspec CLI to select a change that contains delta specs and apply those changes to the main openspec/specs directory.

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 spec changes into main OpenSpec specification files?

To merge delta spec changes into main OpenSpec specification files, run the openspec-sync-specs CLI to read delta Markdown under openspec/changes, apply ADDED, MODIFIED, REMOVED, or RENAMED sections, and update openspec/specs/<capability>/spec.md while preserving unrelated content.

What is the best way to apply change-set updates to canonical OpenSpec specs without copy-paste errors?

Applying change-set updates to canonical OpenSpec specs is best handled by automating intelligent, idempotent merges that read delta and main spec Markdown files, prompt you to select ambiguous changes, and update main specs without overwriting unrelated scenarios.

How does syncing delta specs handle ambiguous change names in the openspec directory?

Syncing delta specs handles ambiguous change names by prompting the user to choose the specific change interactively when the change name is not provided or is ambiguous, ensuring the correct delta is applied to the main specification.

Can I use this merge tool to create new capability spec files from delta changes?

Yes, you can use this merge tool to create new capability spec files. When a delta change introduces a new capability, the tool creates the corresponding openspec/specs/<capability>/spec.md file and produces a concise summary of applied edits for review.

Does merging OpenSpec delta specs preserve existing content in main specification files?

Merging OpenSpec delta specs preserves existing content in main specification files by applying only the targeted delta changes and leaving untouched scenarios and unrelated Markdown content intact during the update process.

What limitations should I expect when removing or renaming requirements across capability specs?

When removing or renaming requirements across capability specs, the tool applies delta spec sections intelligently but requires user guidance for ambiguous changes, meaning manual confirmation is needed if the change name is unclear or multiple matches exist in the repository.