Quick take: AI drafts aren’t bad because the model lacks skill. They’re bad because the model is trying to please you. This prompt flips that dynamic and forces a critique before the output lands in your hands.
The People-Pleaser Problem
AI models are trained on human feedback. And humans tend to reward outputs that feel good to read, not outputs that are actually tight, accurate, or well-structured. Over millions of training cycles, the model learns a simple pattern: make the user happy, get a good rating.
This is the sycophancy trap. u/Significant-Strike40 from r/PromptEngineering put it plainly: the model gives you what it thinks you want to see. That’s not a bug in how you’re prompting. It’s a core behavioral pattern baked into most major models.
The result? Drafts that feel polished but have weak arguments. Reports that read confidently but skip over inconvenient data. Outlines that look complete but repeat the same idea in different sections. The model passed its own vibe check. It didn’t pass yours.
What Recursive Critique Actually Does
The technique shared in the post addresses this directly. Instead of accepting the first draft, you send it back with a structured audit instruction:
Read your draft. Identify 5 logical gaps and 2 style inconsistencies. Rewrite it to be 20% shorter and 2x more impactful.
Each piece of that prompt does a specific job.
- “Identify 5 logical gaps” switches the model from author mode to critic mode. It has to find problems, not defend what it wrote. Five is specific enough to prevent lazy answers like “it could be clearer.”
- “2 style inconsistencies” focuses the critique on tone and voice. Most models default to consistent corporate language, but when you push them to find inconsistencies, they catch things like abrupt tonal shifts or overused filler phrases.
- “20% shorter” is a concrete target. Telling a model to “make it more concise” gets you the same content with shorter words. Giving it a percentage forces actual removal.
- “2x more impactful” sounds vague, but in context it nudges the model to prioritize the strongest arguments and cut the ones that are just filling space.
Together, these constraints pull the model out of approval-seeking mode and put it in editing mode. It can’t just agree with itself.
Is This Just Fancy Editing Advice?
The community called it out: this is essentially “edit your work” packaged as a prompt. Fair point. A human editor would do exactly this, and calling it a “10/10 loop” is a stretch.
But here’s what actually matters. Most people don’t edit AI output. They read the draft, decide it’s good enough, and ship it. Turning structured self-critique into a reproducible prompt lowers the friction enough that people actually use it.
The technique isn’t revolutionary. It’s just the right habit codified into a format that works with how models process instructions.
Use Cases
Where this makes the biggest difference:
- 🔍 Long-form blog posts that feel comprehensive but don’t have a clear argument by the end
- Email drafts where the main ask is buried in paragraph three
- Research summaries that hedge every claim to avoid being wrong
- Landing page copy that sounds confident but doesn’t convert because it never makes a specific promise
- Reports and briefs where the executive summary is just a longer version of the body
💡 Prompt of the Day
Paste this immediately after any AI-generated draft:
Read your draft. Identify 5 logical gaps and 2 style inconsistencies. Rewrite it to be 20% shorter and 2x more impactful.
Want to push a second pass? Add this line: “Now find the single weakest claim in your rewrite. Either support it with a concrete example or remove it entirely.” One more loop, one more layer of quality.
You can also swap the defaults for a specific weakness. “Identify 3 places where I’m hedging unnecessarily and rewrite them to be direct.” Or: “Find 2 sections that repeat the same idea and collapse them into one.” Same structure, different targets.
The Actual Takeaway
AI sycophancy is a real problem that most users never actively counter. The default workflow is prompt, read, accept. The model optimizes for that workflow by producing output that’s smooth enough to pass a first read without ever earning a second one.
Forcing a structured self-critique before you review breaks that pattern. It’s not a magic loop. It’s just applying editing discipline at the model level instead of doing all the editing yourself afterward.
For more takes and variations from the community, check the original thread on r/PromptEngineering.
The ‘Recursive Critique’ 10/10 Loop.
by u/Significant-Strike40 in PromptEngineering