Loop/Prompt Library / Planning & second-opinion review
🔁 Builder + tough reviewer (Claude and Codex)
Claude builds and opens a pull request, Codex reviews it harshly, Claude fixes, and they repeat until it passes.
Use it when: Claude is making a meaningful code change and you want Codex to check each round.
🛑 Stops when: Codex approves, or only accepted issues remain, or the round limit is hit.
Copy this loop
Build [task] and open a pull request. Then ask a different AI (e.g. Codex) for a tough review. Fix every finding at or above [severity, e.g. medium]. Ask for another review. Save the branch, PR, findings, and round number so the run can resume. Stop when the reviewer approves, only accepted issues remain, progress stalls, or after [5] rounds. Never call an errored or timed-out run 'approved'. Report the final verdict.
Review every change the agent makes before you keep it. Set a budget or round limit — the prompt includes one.
Idea from Forward Future's Loop Library · by Lukas Kucinski. Prompt rewritten in plain English by FixKit AI.
More loops like this
Turn an idea into a clear plan
Interviews you about a rough idea, then writes two files: what to build, and how the AI should build and check it.
Make the plan buildable
Fills gaps in a new project's planning docs until two reviewers would build the same thing from them.
Spec review rounds
Writes a spec for one ticket, has a tough reviewer check it against a rubric, and keeps fixing until it is approved.
Devil's advocate review
Has one AI argue your design is wrong, logs every objection, and makes the builder fix or justify each one with proof.
Two AIs must agree
Takes turns having AIs from two different companies review your work until both approve the exact same version.
Done means proven
Writes down every requirement and the proof needed before starting, so half-done work is never reported as done.