skills.rest
valuedriven
valuedrivenCOMMUNITY
Explore all skills by this author →
GitHub

openspec-sync-specs

Merge delta spec changes into canonical main specs.

4|3|Updated Feb 14, 2026
Search Tags:#automation#cli#openspec#change-management#delta-specs#spec-merge
One-click install
npx skills add https://github.com/valuedriven/devai --skill openspec-sync-specs-valuedriven
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/valuedriven/devai/tree/main/.agents/skills/openspec-sync-specs
Command: npx skills add https://github.com/valuedriven/devai --skill openspec-sync-specs-valuedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Core Features & Use Cases

  • Agent-driven delta-merge: read delta specs and apply changes to the canonical main specs with intelligent merging.
  • Supports ADDED, MODIFIED, REMOVED, and RENAMED requirements, including scenario-level changes.
  • Use case: Update main specs by applying a delta spec change without duplicating historical records.

Quick Start

Provide a change name when prompted and initiate the sync flow to apply delta changes to 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 duplicating historical records?▼

To merge delta specs into main specs, use an agent-driven sync flow that applies ADDED, MODIFIED, REMOVED, and RENAMED requirements. It validates both delta and main specs, preserving unchanged content while updating canonical requirements.

What is delta spec synchronization and when do I need it?▼

Delta spec synchronization is the process of applying changes from a delta spec into canonical main specs. You need it when updating main specs with new changes without archiving the original change records.

How do I apply ADDED, MODIFIED, and REMOVED requirements to canonical specs?▼

Apply ADDED, MODIFIED, and REMOVED requirements by initiating a sync flow that guides you through selecting a change, resolving context, and merging scenario-level changes into the main specs.

Can I sync delta specs without archiving the original change?▼

Yes, you can sync delta specs without archiving the change. The sync process updates the main specs by applying delta content while leaving the historical change records intact and unpreserved.

Does the spec merge process preserve unchanged content in main specs?▼

Yes, the spec merge process preserves unchanged content in main specs. It validates delta and main specs before applying targeted updates, ensuring only the specified requirements are merged.

What are the limitations of agent-driven delta spec merging?▼

Agent-driven delta spec merging requires selecting a specific change name to initiate the flow and focuses on applying changes without archiving. It does not duplicate historical records but relies on accurate delta and main spec validation.

Related Skills

Explore More Software Engineering Skills→
rock-hurock-hu

openspec-sync-specs

Merge delta specifications into main OpenSpec repository specs.

Community
Intermediate
kaishinkaishin
10

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and syncing delta specs.

Community
Advanced
luzhenqianluzhenqian
149

openspec-sync-specs

Merge delta specs into main OpenSpec spec files with idempotent updates.

Community
Advanced
remiverdiesenremiverdiesen
6

openspec-sync-specs

Merge delta specification changes into main spec files with an idempotent summary.

Community
Intermediate