openspec-sync-specs

Merge delta specs into main specs with ADDED, MODIFIED, REMOVED, and RENAMED changes.

Updated May 29, 2025
One-click install
npx skills add https://github.com/carlosapgomes/eqmd --skill openspec-sync-specs-carlosapgomes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/carlosapgomes/eqmd/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/carlosapgomes/eqmd --skill openspec-sync-specs-carlosapgomes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often diverge from the main specification as changes accumulate. This Skill provides an automated, agent-driven way to merge delta specs into the canonical main specs, ensuring updates are applied without archiving the delta and preserving existing content.

Core Features & Use Cases

  • Intelligent merging of delta spec changes into main specs (ADDED, MODIFIED, REMOVED, RENAMED) with sensible handling of new and existing scenarios.
  • Idempotent updates: running the operation multiple times yields the same result and prevents duplicate changes.
  • On-demand main spec creation: if a capability/spec does not exist, the tool can create a new main spec and apply ADDED requirements.
  • Guardrails and prompts: if delta context is ambiguous, the agent will prompt for clarification before applying changes.

Quick Start

Run the openspec-sync-specs skill to merge delta specs into main specs and review the updated main specs file.

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?

Merge delta specs into main specs by applying ADDED, MODIFIED, REMOVED, and RENAMED changes directly into the canonical specifications while preserving the original delta files and existing content.

What is a delta specification and when do I need to integrate it?

A delta specification captures incremental changes diverging from the main specification. You need to integrate delta specs when accumulated updates must be applied to canonical specs to maintain a single source of truth.

How do I apply ADDED and MODIFIED requirements to a missing main spec?

When a capability or main spec does not exist, the merge process creates a new main spec on demand and applies ADDED requirements to it, ensuring all delta changes are captured.

Are spec merges idempotent if I run the operation multiple times?

Yes, merging delta specs into main specs is idempotent, meaning running the operation multiple times yields the same result and prevents duplicate changes from being applied to the canonical specifications.

What happens if the delta context is ambiguous during spec management?

If the delta context is ambiguous during spec management, the agent will prompt for clarification before applying changes, ensuring intelligent merging and content preservation without guessing.