AI Compass / Knowledge cards
Separate building and checking
a critic with fresh context
Whoever built something is poorly placed to see their own mistakes. AI agents are similar: the agent that builds has its entire solution path in its context and considers it correct. A critic is a second agent that starts without that history, that is, with fresh context. It checks the result against a yardstick that was set before the build. Jack Roberts shows the pattern as a “gauntlet loop” for design, AI LABS as check skills and a second opinion for code.
What it is for
Mistakes the builder overlooks get noticed before you accept the result. In the end you have to check less yourself.
Steps
- Set the yardstick before the build. For code, that is the original requirements. For design and copy, according to its README the gauntlet-loop repo requires a named model example that the critic can retrieve, such as a particular page or repo. A general grade like “award-worthy design” is not enough.
- Set a checking angle for each critic. Jack Roberts names three: Is the brief fulfilled? Are the design rules followed? Is the craftsmanship clean?
- Start each critic with fresh context, as a subagent or as its own session. For a second opinion, AI LABS uses
claude -pto start a new session without the previous history. - Have it check against the original requirements, not just against one part. An agent that sees only its own part overlooks gaps between the parts.
- Have it compare rather than grade. According to the gauntlet-loop README, the critic places the result and the model example side by side without names and picks the better one, because scores rise from round to round.
- Build, check, improve, until all critics agree. Set a maximum number of rounds yourself, see Limits. In Jack Roberts’s example it was up to 10 rounds.
- For code, use the built-in tools first: according to the docs, Claude Code includes
/code-review(finds bugs),/simplify(cleans up) and/security-review(looks for security vulnerabilities). You only need to build what is missing. At AI LABS, that is a check skill for design.
Limits
- Open contradiction, the critic’s model: Jack Roberts puts the critics on smaller models to save costs. AI LABS warns that a weak checker reports false errors, which cause follow-on costs. My own assessment: for the question “Is this right?” use the strong model; for form and style a smaller one is enough.
- Open contradiction, round limit: According to the gauntlet-loop README, the loop ends only when the result wins the blind comparison or you stop it, never after a fixed number of rounds. I still advise an upper limit, because every round costs tokens.
- Costs: Jack Roberts cites 2 to 3 million tokens per run. That is his figure, not re-measured. The loop is worth it only for important templates.
- Someone else’s design as a model example is a benchmark, not a template to copy. Copyright stays with the original.
- Second opinion from another provider: according to the repo, OpenAI offers a Codex plugin for Claude Code. Your code then goes to OpenAI, which is not suitable for customer code. The route via the Gemini command line from the video of 29 April no longer exists as shown: according to the Google FAQ, since 18 June 2026 it no longer serves requests from personal accounts (Google AI Pro, Ultra and the free version).
- I did not find the Anthropic post that the video of 29 July refers to.
Links
- Checkpoints and gates: the full version with four checkpoints. This card is the light introduction.
- “Done” only with evidence: what a yardstick that can be checked with commands looks like.
- Model choice: cost per task: which model for builder and critic.
- Self-improving loop with locked checks: when the yardstick has to stay fixed over many rounds.
Sources
- Jack Roberts: Claude Design just got 10X Better… I’m Done, 10 August 2026, 1:52-5:52, 9:39-11:29. Self-promotion for the community, plus a Glaido link
- AI LABS: Anthropic Just Fixed Graph Engineering’s Greatest Flaw, 29 July 2026, 5:53-13:29. Sponsored by SerpApi, plus a paid community
- Jack Roberts: Claude Code just got 10X Better (Codex + Gemini), 29 April 2026, 6:58-8:37, 12:24-13:30. Self-promotion (masterclass in the community), plus a Glaido link
- robonuggets: gauntlet-loop, README (licence CC BY 4.0, idea by Matt Shumer), retrieved 17 October 2026
- OpenAI: codex-plugin-cc, retrieved 17 October 2026
- Claude Code docs: Commands (
/code-review,/simplify,/security-review), retrieved 17 October 2026 - Google: Gemini Code Assist, note on personal accounts, retrieved 17 October 2026
Status
Checked 17 October 2026 · Maturity new (pattern available, check commands in the docs; costs and effect only from the creators)
Want to try this with your team? That’s what the AI Lab is for. See the AI Lab