doubt
Audits the implementation against its own claims, with no write access at all.
- Model
- opus
- Tools
- ReadGrepGlobBash(git *)Bash(pnpm *)Bash(node *)Bash(ls *)Bash(cat *)Bash(rg *)Bash(curl *)
- Definition
- .claude/agents/doubt.md
- Project
- agent-harness
- Cost
- One Opus pass plus a full re-run of the verification matrix, so it is the most expensive stage. That is the trade.
WHEN IT RUNS
Read-only adversarial auditor for the SPID Doubt stage. Verifies claims in .buildloop/build-claims.md against the actual code and re-runs the verification matrix. Use after any implementation that makes verifiable claims. Reports findings; never fixes them.
CONTEXT
.buildloop/build-claims.md, the delta manifest it names, and the repo. It re-runs every check in the verification matrix itself rather than believing the row that says PASS.
MEMORY
None. It writes .buildloop/review-report.md; a separate agent holds the pen that fixes anything.
EVALUATION
Every finding carries a severity, a file:line, the exact command run, its actual output, and what was expected. A finding it did not reproduce does not get reported.
WHERE IT FAILS · 3
- Invents findings to look useful. A rubber-stamp audit and a real one are indistinguishable from outside, so credibility is the only signal — and this is the way to spend it.
- Reads an exit code instead of the output, and calls a command that ran a behaviour that is right.
- Misses the class it exists for: a claim that compiles and is no longer true.
LESSONS · 1
- The read-only tool grant is the whole design. An auditor with a pen fixes a failing check by editing the check, every time, because that is the cheapest repair available to it.
CONNECTED · 2
SEE THE GRAPH- MCPzckr-labuses — The lab itself as tools: projects, the agent and MCP registries, the infrastructure inventory, the graph joining them, notes, the stack, the monthly snapshot, ideas and search — read-only, over the same validated content the pages render.
- PROJECTAgent Harnessbelongs to — The root Claude Code setup every other project inherits: the shared constitution, the skills, and the build loop that runs a spec to done.