Honest answer: often, no. Loops are powerful, and like most powerful tools they're frequently unnecessary. Four boxes decide whether a task deserves one — and when it doesn't, there are two other routes that fit better. Ten seconds of checking replaces an hour of ceremony.
Box two is the gatekeeper. A loop is only as good as its checks, and checks must be falsifiable — countable, matchable, verifiable. "Under 120 words" qualifies; "sounds like me" doesn't, and no loop can save it. Chapter 02 showed what happens when checks go soft: accuracy fell off a cliff and correct work got destroyed.
There's also a shortcut version of this test, courtesy of the practitioners: the moment you catch yourself thinking "I'll have to try a lot of variations," that's the loop signal. Your instinct has already answered the four boxes.
Work with hard requirements someone will hold you to: the description that must name the price, the report that must cite every figure, the code that must pass tests, the Friday deliverable. Write the six-label file from Chapter 02 and let it run. If it repeats, the five-minute setup amortizes to zero.
Names, headlines, hooks, subject lines, one-liners. Don't refine one draft in circles — generate three independent candidates, grade them against your criteria, keep the winner. For short work this measurably beats polishing the same draft, and it takes one message:
Give me 3 independent options for [the thing]. Then grade each against: [your 2–3 criteria]. Tell me which wins and why, quoting the evidence.
Design, voice, creative direction — anywhere "done" is a judgment call. Rubric theater doesn't help here; react to what you see, one round at a time, like an editor. The craftsmanship layer (length, structure, required beats) can still be looped — the taste calls stay yours.
Quick answers, brainstorms, casual emails, summaries you'll skim. The four decisions from Chapter 01 buy a strong single attempt — take it and move on. Adding a loop here is bureaucracy.
Two situations genuinely straddle the routes. Creative work: you can't check "is this moving?" — but you can check structure: length, point of view, required beats, banned clichés. Run a loop for the checkable layer, then judge the result like an editor. Research and analysis: "is this true?" is hard to self-check, but "does every claim have a source?" and "are all five competitors covered?" are countable. Loop the coverage and the sourcing; keep the judgment.
Once loops click, the temptation is to loop everything — and an unnecessary loop isn't just wasted setup. It adds passes where one attempt was fine, manufactures checks for things that didn't need checking, and slowly teaches you to distrust good-enough first drafts. The builders quoted in Chapter 02 don't loop their lunch orders. The skill isn't running loops; it's knowing which work deserves one.
Run the four boxes on the task you're avoiding right now. Whatever route it lands on, you'll finish faster. When you'd rather have the spec or the loop written for you, that's the tool we build.
Try Prompt Optimizer