Loop/Prompt Library / Planning & second-opinion review
🔁 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.
Use it when: A ticket is too risky or vague to start coding yet.
🛑 Stops when: The reviewer says 'ready' with no major issues, or the round limit is hit and the blocker is logged.
Copy this loop
For ticket [ticket], write a spec packet: findings, task plan, progress notes, and a grading rubric with must-pass checks and edge cases from the ticket. Check any facts against the repo. Then have a separate reviewer grade it against the rubric and confirm old issues stay fixed. Fix every issue across all files, log the issue and fix, and review again. Stop when the reviewer says 'ready', or after [5] rounds with the blocker logged for me.
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 Ximanta (@kharamdau). 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.
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.
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.
Done means proven
Writes down every requirement and the proof needed before starting, so half-done work is never reported as done.