skills.rest
agentxm
agentxmOFFICIAL
Explore all skills by this author →
Website𝕏@agentxm_aiGitHub

openspec-sync-specs

Merge delta-spec changes into main OpenSpec specs idempotently.

5|Updated Jan 29, 2026
Search Tags:#automation#merge#openspec#delta-specs#spec-merging#main-spec
One-click install
npx skills add https://github.com/agentxm/axm --skill openspec-sync-specs-agentxm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-sync-specs
Source: https://github.com/agentxm/axm/tree/main/.gemini/skills/openspec-sync-specs
Command: npx skills add https://github.com/agentxm/axm --skill openspec-sync-specs-agentxm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specs created during development often exist in isolation from the canonical main specs, leading to drift and manual integration overhead. This skill provides an auditable, delta-driven workflow to merge delta changes into the main specification while preserving existing content.

Core Features & Use Cases

  • Intelligent merging reads delta blocks and applies changes to corresponding main specs, preserving untouched content.
  • Supports ADDED, MODIFIED, REMOVED, and RENAMED sections with an idempotent merge strategy.
  • Best for teams maintaining shared OpenSpec docs; when a capability has no main spec, it can create one with a defined purpose and initial requirements.

Quick Start

Run the delta-merge workflow to synchronize delta specs into the main specification.

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 in OpenSpec?▼

Merge delta specs by identifying changes in openspec/changes and applying them to corresponding main specs under openspec/specs. The process adds new scenarios, updates existing ones, and handles renamed or removed requirements while preserving untouched content.

What happens when a delta spec has no existing main spec to merge into?▼

When a capability has no main spec, the merge process creates a new one automatically. It initializes the new main spec with a defined purpose and incorporates the ADDED requirements from the delta spec.

Can I run delta-spec merging multiple times without duplicating content?▼

Yes, the delta-spec merging strategy is idempotent. Running the merge workflow multiple times applies changes intelligently without duplicating content, ensuring the main specs reach a consistent state.

What types of requirement changes can be synchronized from delta specs to main specs?▼

Delta spec synchronization supports ADDED, MODIFIED, REMOVED, and RENAMED sections. It applies these changes to the main specification while preserving existing content that the delta does not explicitly target.

Why do my OpenSpec main specs drift from the changes made during development?▼

Main specs drift because delta specs created during development often exist in isolation from the canonical main specs. Merging these delta changes provides an auditable workflow to synchronize the main specification and eliminate manual integration overhead.

Related Skills

Explore More Software Engineering Skills→
AdJIaAdJIa

openspec-sync-specs

Merge delta spec changes into main OpenSpec specs idempotently.

Community
Advanced
oalansilvaoalansilva

openspec-sync-specs

Merge delta specifications into main specs while preserving existing content.

Community
Advanced
agoodwayagoodway

openspec-sync-specs

Merge incremental OpenSpec delta requirements into main capability spec files.

Official
Intermediate
carlosapgomescarlosapgomes

openspec-sync-specs

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

Community
Advanced