Loop/Prompt Library / Planning & second-opinion review
🔁 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.
Use it when: Your idea is too fuzzy to hand to an AI for a long solo run.
🛑 Stops when: Both plan files exist, every 'done' check can be tested, and nothing important is undecided. Or it says 'not ready'.
Copy this loop
I have a rough idea: [idea]. Ask me questions one at a time until it is clear (at most [10] questions). Then write SPEC.md: what to build, what not to build, and testable 'done when' checks. Write GOAL.md: the work plan, a progress scorecard, quick and final checks, where to keep notes, and what needs my approval. If any key decision, tool, or permission is missing, mark it 'not ready' and stop. Do not start building until I approve.
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 michael Guo (@michaelzsguo). Prompt rewritten in plain English by FixKit AI.
More loops like this
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.
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.