openspec-sync-specs

Merge delta specs into main OpenSpec specifications deterministically.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to synchronize delta specs into the main specification, preserving changes while avoiding archival of the delta.

Core Features & Use Cases

  • Intelligent merging of delta specs into main specs to reflect added, modified, removed, and renamed requirements without wholesale replacement.
  • Preservation of context: unrelated content in main specs remains untouched to maintain continuity across revisions and workflows.
  • Use Case: When a delta spec introduces small corrections or additions, the tool merges only the intended changes, keeping the rest of the main spec stable.

Quick Start

  • List available changes with openspec list --json to see available changes.
  • Identify the delta spec to apply under openspec/changes/<change-name>/specs/.
  • Apply changes to the main specs following the delta spec's guidance.

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?

Use the openspec list --json command to identify available delta specs, locate the target delta under openspec/changes/<change-name>/specs/, and apply its changes to the main specs following the delta spec's merging guidelines.

Can I synchronize renamed and removed requirements using delta-to-main spec merging?

Yes, delta-to-main spec merging handles renamed and removed requirements deterministically, applying targeted changes to the main specification without wholesale replacement or archival of the original delta spec.

Do I need the openspec CLI to apply delta spec changes to main specifications?

Yes, the openspec CLI is required to list available changes with openspec list --json and to read both delta and main specs to apply changes deterministically across OpenSpec projects.

What is the best way to apply small corrections to a main spec without rewriting it entirely?

Unlike wholesale replacement, OpenSpec delta-to-main merging applies only the specific added, modified, removed, and renamed requirements from the delta spec while deterministically preserving all unrelated content in the main specification.

What happens to the delta spec after merging it into the main specification?

After merging a delta spec into the main specification, the delta is preserved and avoids archival, maintaining continuity across revisions and workflows for future reference.