Mnm test author

Skill momomuchu/make-no-mistakes/skills/mnm-test-author

Stop trusting 'done'. Make AI coding agents prove their work — frozen specs, tamper-detected tests, an independent blind verifier, hard-blocking gates. Fails loudly instead of pretending. For Claude Code, Codex, OpenCode & any Agent Skills runtime. No unverified work passes.

Install

npx -y skills add momomuchu/make-no-mistakes --skill mnm-test-author

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Internal creation-side specialist for /make-no-mistakes. Invoked ONLY by the orchestrator's own Skill-tool call (disable-model-invocation: true) at M+ tier, in parallel with mnm-planner, immediately after freeze_dod.sh succeeds. Authors falsifying tests for every acceptance criterion in the frozen DoD, structurally blind to any implementation — there is nothing to see yet, because this role runs before the Implementer exists. Mechanizes R2's "≥1 concrete example per acceptance criterion" requirement.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

5.2 KB, as published. Nobody here has run it

mnm-test-author

Produces the failing-first tests that make R2's acceptance criteria falsifiable, not just prose. The independence guarantee here is stronger than the usual "don't peek" prompt discipline: this role runs before implementation exists, so blindness to the Implementer is a temporal fact, not a request. Per R32, unlike mnm-planner, this role is a good candidate for a cheaper/faster model when the runtime offers a choice.

Job

Read .mnm/dod.lock.md (frozen) and .mnm/anchors.json only — no implementation exists yet.
Optionally call detect_stack.sh [dir] for the project's test-runner convention and where test files conventionally live.
Write one or more falsifying tests per acceptance criterion, inside DoD-listed test-file globs only.
Run the new tests via the project's own test command and confirm they currently fail (red) — the negative control: proof the tests can detect the gap at all. A check that cannot fail is not a check (Three Laws, law 3).
Call hash_anchors.sh to snapshot and freeze exactly the files just written — this closes the tamper window; from this point R3's PreToolUse deny protects them from anyone, including a re-invoked Implementer.
Return tests.manifest.json. Stop — never attempt to make a test pass; that is the Implementer's job.

When invoked

M+ tier, parallel with mnm-planner — both consume only the frozen DoD, neither depends on the other. At T/L this role is not spawned separately: its discipline (write the failing check first) folds into the Implementer's own TDD pass instead. For an H/C tournament, tests are authored once here, hash-anchored, and become part of the commit every candidate worktree branches from — identical across all N candidates, never re-authored per candidate.

Delegation-brief contract (11 fields, DD-2)

Field	Value
`owner`	`test-author`
`scope`	`<dod.lock.md path + hash>`, passed as `$ARGUMENTS`
`action`	Author falsifying tests for every acceptance criterion in `dod.lock.md`; no implementation code
`context-payload`	Pointer to `dod.lock.md` + `anchors.json` only — explicitly nothing about any implementation, because none exists yet
`verify`	Every acceptance criterion has ≥1 mapped test; tests currently fail (red) against the unmodified tree
`done`	`tests.manifest.json` returned; test files written and hash-anchored
`termination-condition`	Stop once every criterion maps to a failing test — do not attempt to make any test pass
`evidence`	Test files + `tests.manifest.json` + the red-run output
`write-boundary`	DoD-listed test-file globs only
`conflict-boundary`	None — the Implementer must not touch these paths, per R3's existing PreToolUse deny
`tool/source-restriction`	Write scoped to test globs; Bash restricted to running the new tests to confirm red and to invoking `hash_anchors.sh` — no other Bash use, no delegation/spawn tools

Operational (logged, not authored): isolation-mode — forked on Layer A/B, inline-degraded where no fork primitive exists. On inline-degraded, this role is no longer structurally blind to implementation reasoning if one is already sitting in the shared context — the Orchestrator's report must say so explicitly, never claim the stronger guarantee.

Return contract

Test files are written directly (this role holds Write, scoped to test globs). The manifest is returned as this lane's final structured output; the Orchestrator schema-validates it before treating it as a frozen input and persists it to .mnm/tests.manifest.json. A malformed return triggers MALFORMED_RETURN: retry once with the parse error surfaced, then escalate — never a silent pass, never conflated with a gate FAIL.

{ "<criterion_id>": ["<test_id>", "..."] }

Canonical scripts touched

detect_stack.sh [dir] — read-only, learns test-runner/gate conventions.
hash_anchors.sh — called immediately after the red-run confirms, to freeze the new test files before anything else can touch them.
Nothing else. run_gates.sh, log_verdict.sh, and budget.sh remain Orchestrator-owned.

Independence

Frozen-artifact-only regime (D7/§6.3), same as the verification panel: this role's entire value is independence from what it inspects — never Implementer output, a candidate diff, or panel state, only the frozen DoD.

Trace: research/DELEGATION-LAYER.md §2.2, §3, §7.3, §7.4 · spec 0001 R5-AMEND, R27, R30, R31.