skills.rest
MoonCoder-HAPPY
MoonCoder-HAPPYCOMMUNITY
Explore all skills by this author →
GitHub

specdo-sync

Merge delta specification blocks into main specs for active spec_change.

Updated Aug 27, 2026
Search Tags:#change-management#delta-specs#main-spec#specdo-sync#transactional-write#verification-payload
One-click install
npx skills add https://github.com/MoonCoder-HAPPY/SpecDo --skill specdo-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specdo-sync
Source: https://github.com/MoonCoder-HAPPY/SpecDo/tree/main/specdo-sync
Command: npx skills add https://github.com/MoonCoder-HAPPY/SpecDo --skill specdo-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

SpecDo Sync solves the challenge of consistently merging delta specifications into the main specification for an active spec_change, ensuring changes are applied in a controlled, auditable way.

Core Features & Use Cases

  • Transactional delta merge: merges ADDED, MODIFIED, REMOVED, and RENAMED blocks into the main specs with safeguards.
  • Validation-driven routing: enforces lifecycle and verification gates, and routes to apply, propose, or archive as needed.
  • Guarded by active-change rules: only operates on active spec_change and respects workspace, target, and artifact quality constraints.

Quick Start

Run the sync against an active change to merge delta specs into the main specification.

Frequently Asked Questions about specdo-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge delta specifications into the main spec?▼

To merge delta specifications into the main spec, run a sync against an active spec_change. This process combines ADDED, MODIFIED, REMOVED, and RENAMED blocks into the main specs using transactional writes.

What is a transactional write for delta specs?▼

A transactional write for delta specs applies merged block changes to the main specification only when a valid sync_readiness payload is present. This ensures specification changes are applied in a controlled, auditable manner.

Can I sync delta specs into an archived target?▼

You cannot sync delta specs into an archived target. The merge process enforces guards around archived targets, workspace validity, and verification requirements, operating strictly on active changes.

Why does validation-driven routing redirect my spec change?▼

Validation-driven routing redirects your spec change because it enforces lifecycle and verification gates. Based on payload validity, it routes the workflow to apply, propose, or archive as needed.

When do I need a sync_readiness payload for specification changes?▼

You need a sync_readiness payload for specification changes when you want to commit merged delta blocks transactionally. The main spec is written only when this valid verification payload is present.

Related Skills

Explore More Software Engineering Skills→
a-ariffa-ariff
14

executing-plans

Execute implementation plans in batches with verification gates and status tracking.

Community
Intermediate
statick88statick88
1

sdd-archive

Merge delta specifications into main specs and archive completed change folders.

Community
Advanced
slavochek2slavochek2
1

mutate-stories

Mutate stories, points, and related rows with replay-detection and commit gates.

Community
Advanced
wonderslifewonderslife
13

openspec-sync-specs

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

Community
Advanced