Mariomarquezt

Multi Build — Testing skill for Claude Code

Testing community

Claude Code skill that builds one new feature with several AI models at once: a spec with testable acceptance criteria and agreed interfaces first, the work split by file across the models, each part.

How to install Multi Build

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Mariomarquezt/multi-build and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Multi Build does

Alternatives in Testing

Adversarial Spec — A Claude Code plugin that iteratively refines product specifications by debating between multiple LLMs until a 514 ★
Create E2e — Create a Playwright E2E test with explicit success criteria 335 ★
Toh Framework — Type one sentence, approve once, walk away — Toh Framework installs an AI build department (14 commands, 8 age 94 ★

README

multi-build

**Version 1.0.0** — see [`CHANGELOG.md`](CHANGELOG.md). Your installed version is the `version:` line in `SKILL.md`.

A Claude Code skill that builds **one new feature** with several AI models at once. It writes a spec with acceptance criteria you can test, agrees the interfaces between the parts before anyone codes, splits the work by file evenly across the models, has each builder write the failing test first, has a **different** model on a **different** subscription review every part against the spec, integrates, runs the full suite, and makes one commit.

**The one idea:** parallel building fails at the joins. Each builder makes a private assumption about the seam between its part and the next, and the assumptions disagree. So the seams — signatures, data shapes, routes — are written first, and every brief carries them word for word. Builders fill in behind a contract; they do not invent one.

Sister skills: [`multi-fix`](https://github.com/Mariomarquezt/multi-fix) fixes a list of defects the same way; [`sliced-review`](https://github.com/Mariomarquezt/sliced-review) finds them. All three share one rule: the model that wrote something never checks it, and the check is never on the same bill.

Install

git clone https://github.com/Mariomarquezt/multi-build ~/.claude/skills/multi-build

Recommended alongside it: [`sliced-review`](https://github.com/Mariomarquezt/sliced-review), for the backend wiring notes (`references/runners.md`) this skill points at.

Modes

The number is how many models take part.

you type	who builds	who reviews	use it when
`/multi-build 2`	Sol	Grok	a small feature, one or two files
`/multi-build` or `/multi-build 3`	Sol, Grok, Opus — equal shares	each reviews the next, A→B→C→A	the normal case
`/multi-build 5`	those three + GLM Flash + Composer — equal shares	fixed ring Sol → Opus → Grok → GLM → Composer → Sol	a large feature with many separable parts