What the source did
- Muse and Codex agents build; Grok agents review every lane.
- A third failed review triggers a redesign instead of another patch.
“the model that writes a lane never reviews it”— Randy Northrup (@starsoldier420), X
Summary written by Agent Cookbook. See the original for the full context.
Get their template
Made and published by Randy Northrup. Start here; it is their original, not ours.
Our adapted version
Ours Our version, based on what Randy Northrup described. Not their wording. Fill in the [BRACKETS].
REVIEWER (different model than the author):
You did not write this. Review lane [NAME] against its spec [FILE].
Return PASS or FAIL with numbered reasons. This is review #[N].
If N = 3 and still FAIL, don't suggest patches: write a one-paragraph redesign proposal instead.
Approval rule
🛡
Nothing merges without a PASS from a non-author model and your sign-off.
Set it up
- Label each work item with its author model.
- Route reviews to a different vendor.
- Track the review count per item.
Common failures
⚠
- Same-model reviewers rubber-stamp shared blind spots.
- Endless patch loops without the 3-strike rule.
Variations
- Use Grok Bot as reviewer for Claude Code work.
- Apply to docs and specs, not just code.
Get the 10 best agent setups. Free.
Plus new recipes every week. One email, no spam.
Unsubscribe anytime. Privacy