openspec-sync-specs

Merge delta spec changes into main specs while preserving unrelated content.

6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill openspec-sync-specs-jacobcy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/.github/skills/openspec-sync-specs
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill openspec-sync-specs-jacobcy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs drift and must be reconciled with the main specs. This skill centralizes delta-to-main spec merging, enabling safe updates without archiving the delta.

Core Features & Use Cases

  • Delta-aware merging: reads delta specs and applies changes to the corresponding main specs.
  • Intelligent conflict handling: merges ADDED, MODIFIED, REMOVED, and RENAMED requirements while preserving unrelated content.
  • Auto-create when missing: creates a new main spec file if a capability does not yet exist.

Quick Start

Run the openspec-sync-specs agent to merge delta specs into the 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 delta specs into main specs without losing unrelated content?

Use delta-aware merging to apply ADDED, MODIFIED, REMOVED, and RENAMED requirements to main specs, which preserves unrelated content and reconciles drift without archiving the original delta spec.

What is the best way to sync delta-based spec changes across multiple capabilities?

The best way to sync delta-based spec changes is to run an automated agent that reads delta specs and current main specs, applying changes across multiple capabilities while auto-creating missing main spec files.

Can I update main specs from a delta spec without archiving the change?

Yes, you can update main specs without archiving the change by using a centralized delta-to-main merge process that applies delta requirements directly to the main spec files, leaving the delta intact.

Does spec syncing automatically create a new main spec file if a capability does not exist?

Yes, spec syncing automatically creates a new main spec file if a capability referenced in the delta does not yet exist, ensuring new capabilities are properly established in the main specs.

How does intelligent spec merging handle REMOVED and RENAMED requirements?

Intelligent spec merging handles REMOVED and RENAMED requirements by reading the delta spec and applying those specific structural changes to the current main specs, updating the document while keeping unrelated sections intact.