openspec-sync-specs

Merge delta specifications into main OpenSpec specs with non-destructive updates.

503|60|Updated Sep 7, 2023
One-click install
npx skills add https://github.com/epam/ai-dial-chat --skill openspec-sync-specs-epam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/epam/ai-dial-chat/tree/main/.claude/skills/openspec-sync-specs
Command: npx skills add https://github.com/epam/ai-dial-chat --skill openspec-sync-specs-epam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs often diverge from main specs; this skill provides an automated, non-destructive way to merge delta changes into the canonical OpenSpec specs across a repository.

Core Features & Use Cases

  • Intelligent, delta-driven merging of ADDED, MODIFIED, REMOVED, and RENAMED requirements to update main specs.
  • Works with delta spec files produced from the openspec CLI, guiding user prompts and status checks to ensure correct context.
  • Keeps existing content intact by applying changes incrementally and idempotently.

Quick Start

Provide a delta spec path or change name to begin syncing delta specs into 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 OpenSpec delta specs into main specs without losing existing content?

To merge OpenSpec delta specs non-destructively, this skill intelligently applies ADDED, MODIFIED, REMOVED, and RENAMED requirements incrementally to update main specs while preserving existing content.

What is a delta specification in OpenSpec?

A delta specification captures changes diverging from canonical OpenSpec specs, categorizing requirements as ADDED, MODIFIED, REMOVED, or RENAMED to guide automated, idempotent reconciliation.

Do I need the openspec CLI installed to sync delta specifications?

Yes, the openspec CLI must be installed to sync delta specifications, as this skill relies on its delta spec files, status checks, and parsing to guide the reconciliation process.

How do I apply delta spec changes across repository-local OpenSpec requirements?

You provide a delta spec path or change name, and the skill performs status checks, parses the delta, and carefully reconciles changes across repo-local specs to ensure idempotent updates.

Can I rename requirements in OpenSpec without breaking existing specs?

Yes, the skill handles RENAMED requirements during delta syncing by carefully applying non-destructive updates, preserving existing content while applying changes incrementally.