🧩
AutomationJavaScript

Spec Merger

by MageByte-Zero

Spec Merger is an Automation skill for Claude Code, published by MageByte-Zero in spec-superflow.

759 stars75 forkson MageByte-Zero/spec-superflowAdded 2026/08/23+1% in starsRepository updated 2026/08/16
ai-codingamazon-qclaude-codeclinecodexcopilot-clicursorgemini-cliopencodeopensourceopenspecskillsspec-driven-developmentspec-firstsuperpowerstddtraewindsurfworkflow
Install in seconds
Install Spec Merger
Copy Spec Merger into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/MageByte-Zero/spec-superflow/tree/main/skills/spec-merger ~/.claude/skills/spec-merger

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/MageByte-Zero/spec-superflow.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/spec-merger/SKILL.md in MageByte-Zero/spec-superflow
Installs to
~/.claude/skills/spec-merger
Collection
One of 9 skills cataloged from this repository
Category
Automation — 2226 skills

What Spec Merger does

Spec Merger syncs delta specs into the published main spec base before a change closes. Use it when a change is still executing or when spec drift needs to be merged and conflicts checked.

Spec Merger is cataloged under Automation on DirSkills. Spec Merger comes from a repository tagged ai-coding, amazon-q, claude-code, cline and codex.

Documentation

README

Spec Merger

Before the final executing → closing transition, delta specs (ADDED/MODIFIED/REMOVED/RENAMED) must be published into the main spec base. changes/<change>/ remains the active workflow source; root specs/ is only the published baseline. Specs that aren't synced become lies. A change already in closing must not be routed to spec-merger.

Execution-State Guard

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Spec Merger

  • What else does MageByte-Zero publish alongside Spec Merger?

    Spec Merger is one of 9 skills that DirSkills catalogs from MageByte-Zero/spec-superflow, the repository it ships in. Its siblings there include Bug Investigator, Build Executor and Code Reviewer. Each one is a separate skill with its own page in this directory, installs the same way Spec Merger does, and is maintained by MageByte-Zero in that same repository. The rest of the collection is listed on the MageByte-Zero/spec-superflow page.

  • How does Spec Merger compare to other Automation skills?

    Spec Merger ranks #1040 by stars among the 2226 Automation skills in this catalog. The most-starred ones next to it are Autonomous Loops, Autonomous Agent Harness and Automation Audit Ops. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Spec Merger against them. Open each page to compare what they document and how they install.

More from MageByte-Zero/spec-superflow

Spec Merger is one of 9 skills cataloged on DirSkills from MageByte-Zero/spec-superflow.

See all 9 skills →
🔎
2026/08/23

Bug Investigator

Bug Investigator guides systematic root-cause debugging for bugs, test failures, and unexpected behavior before any fix is proposed. Use it when execution is blocked or the cause is unclear.
Quality
75975
🛠️
2026/08/23

Build Executor

Build Executor governs implementation from an approved execution contract and supports disciplined build work, TDD execution, and guarded batch-by-batch changes. Use it when work must follow approved tasks, verification steps, and branch isolation rules.
Quality
75975
🔍
2026/08/23

Code Reviewer

Code Reviewer reviews completed implementation batches for spec compliance and code quality. Use it after execution waves, before merging, or at a review gate to verify changes and act on feedback.
Quality
75975
📄
2026/08/23

Contract Builder

Contract Builder converts approved planning artifacts into a single execution contract for implementation. Use it when moving from planning to build or when the current execution contract is missing or stale.
Automation
75975
🧭
2026/08/23

Need Explorer

Need Explorer clarifies intent, scope, constraints, and success criteria before artifacts are written. Use it when a request is fuzzy, options need comparison, or a stable change definition is needed first.
AI Engineering
75975
📦
2026/08/23

Release Archivist

Release Archivist closes a spec-superflow change with verification, audit, and archive readiness. Use it when implementation is complete or a final wrap-up is needed before moving to closing.
DevOps
75975