skills.rest
kunish
kunishCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-sync-specs

Merge delta specs into main OpenSpec specs with idempotent rules.

Updated Mar 4, 2026
Search Tags:#automation#merge#openspec#delta#specs#version-control
One-click install
npx skills add https://github.com/kunish/muon --skill openspec-sync-specs-kunish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/kunish/muon/tree/main/.github/skills/openspec-sync-specs
Command: npx skills add https://github.com/kunish/muon --skill openspec-sync-specs-kunish

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 merging of delta specs into main specs with intelligent conflict resolution and guardrails.
  • Supports ADDED, MODIFIED, REMOVED, and RENAMED changes, preserving untouched content.
  • Ensures idempotent operations and provides a clear summary after synchronization.

Quick Start

Run openspec list --json to identify available delta changes, then execute the merge per delta spec to synchronize 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 sync delta specs to main specs without archiving the change?▼

Delta spec syncing merges incremental changes from openspec/changes into main openspec/specs using intelligent rules for ADDED, MODIFIED, REMOVED, and RENAMED requirements, preserving untouched content without archiving the change.

What is the best way to merge ADDED and MODIFIED requirements in openspec delta specs?▼

Intelligent delta merging applies rules for ADDED, MODIFIED, REMOVED, and RENAMED requirements from the delta format into main specs, ensuring untouched content is preserved during the synchronization.

How do I list available delta changes for version-control before merging specs?▼

Run openspec list --json to identify available delta changes, which outputs the names of changes ready to be merged into your main specifications during version-control workflows.

Does the openspec delta merge process support idempotent operations?▼

Yes, the openspec delta merge ensures idempotent operations, meaning running the synchronization multiple times yields the same final state and provides a clear summary of updates.

Do I need the OpenSpec CLI to automate delta spec synchronization?▼

Yes, the OpenSpec CLI is required to identify available delta changes and execute the agent-driven merge operation into main specs, ensuring safe and idempotent synchronization.

What happens to untouched content when syncing REMOVED requirements in delta specs?▼

When syncing REMOVED requirements, the intelligent merge preserves existing content not mentioned in the delta, ensuring only targeted specifications are updated without affecting untouched content.

Related Skills

Explore More Software Engineering Skills→
daodaoedudaodaoedu

openspec-archive-change

Archive completed OpenSpec change directories after validating artifacts and tasks.

Official
Advanced
ywh0606ywh0606

opsx-sync

Sync delta specification changes into the main specification repository.

Community
Intermediate
carlosapgomescarlosapgomes

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced
carlosapgomescarlosapgomes

openspec-sync-specs

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

Community
Advanced