openspec-sync-specs

Merge delta specs into main OpenSpec specification files.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-sync-specs-hongquandev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/hongquandev/OpenSpec-VI/tree/main/.agent/skills/openspec-sync-specs
Command: npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-sync-specs-hongquandev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs describe changes that should be applied to main specifications. This tool reads delta specs and directly updates the main specs to apply the changes, reducing manual patching and preserving a clean history.

Core Features & Use Cases

  • Delta-driven merging: reads delta specs and directly updates main specs to apply changes.
  • User-guided delta selection: ensures the user explicitly selects which delta to apply, avoiding automatic guessing.
  • Safe, idempotent merges: applies changes in a way that repeated runs produce the same result and preserves content not mentioned in the delta.
  • Scope: handles additions, modifications, removals, and renames across capabilities.

Quick Start

Run the delta-to-main spec sync workflow to apply the chosen delta spec into the main specifications and verify the merged outcome.

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 automatically?

To merge delta specs into main specs automatically, run the delta-to-main spec sync workflow to apply changes from openspec/changes/<name>/specs/*/spec.md directly to openspec/specs/<capability>/spec.md, producing an updated main specification.

What is a delta spec in software specification management?

A delta spec is a specification file describing added, modified, removed, or renamed requirements across multiple capabilities, designed to be applied to main specs to finalize changes without manual patching and preserve a clean history.

Does merging delta specs require manual change selection?

Yes, delta spec merging requires explicit user validation for change selection, ensuring you select which delta to apply to avoid automatic guessing and maintain control over the main spec updates.

Are repeated delta spec merges safe for existing main specs?

Repeated delta spec merges are safe and idempotent, meaning multiple runs produce the same result while preserving existing main spec content not mentioned in the delta changes.

What types of requirement changes can delta specs handle?

Delta specs can handle additions, modifications, removals, and renames across multiple capabilities, reading from openspec/changes directories and applying them to the corresponding openspec/specs capability files.

What is the best way to finalize openspec changes without manual patching?

The best way to finalize openspec changes without manual patching is using a delta-driven merging tool that reads delta specs and directly updates main specs, requiring explicit user validation to select the correct delta.