Most people treat AI conversations like a vending machine. Put in a question, get an answer, move on. But what if the real value comes from what happens after that first response?
I keep running into prompting techniques that sound almost too simple to work, and then they do. This Reddit contributor shared a pattern on r/PromptEngineering that flips the usual one-shot workflow into something much more powerful. The idea is straightforward: instead of accepting Claude’s first answer, you ask it to critique and improve its own reasoning.
🧭 Quick Start
What you’ll learn: A simple iterative prompting pattern that consistently produces stronger, more accurate AI responses.
What you need: Access to Claude (or any capable LLM). No tools, no plugins, no setup.
Time to implement: About 30 seconds per interaction.
The Old Way vs. The New Way
Here’s how most people prompt:
- Question → Answer → Done
You ask something, you get a response, you move on. The problem? That first answer often contains assumptions, gaps, or surface-level reasoning that you never catch.
The approach this Redditor recommends looks like this:
- Question → Answer → Critique → Refinement
One extra step. That’s it. And the results are, honestly, noticeably better.
📋 Step-by-Step: The Self-Critique Loop
Step 1: Ask your question normally. Just prompt Claude with whatever you need. Don’t overthink the initial query. This first response gives the model a foundation to work from.
Step 2: Follow up with the critique prompt. After you get the first answer, paste this exact follow-up:
Identify the weakest assumptions in your previous answer and improve them.
Why this works: Claude is particularly strong at self-evaluation. When you explicitly ask it to find holes in its own logic, it activates a different kind of reasoning. The original poster notes that “the second answer is often significantly stronger” because the model is now stress-testing its own output instead of generating from scratch.
Step 3: Review the refined answer. The second response should address gaps, strengthen weak points, and provide more nuanced reasoning. You can repeat the loop if needed, but one round of critique usually delivers the biggest improvement.
🔑 Community Tips That Make This Even Better
The discussion thread added a few tricks worth noting:
- Ask for re-summarization. One commenter mentioned that asking Claude to “summarize again” forces it to distill and sharpen its points. You can also feed in new information and ask it to “look at things from another angle.”
- Add context between rounds. Instead of just asking for critique, you can inject additional details or constraints. This gives the model new material to work with during refinement.
- Try the “fresh eyes” technique. One savvy commenter shared an advanced version of this loop: take the first answer, paste it into a brand new session as a document, and ask Claude to critique it without knowing it wrote the original. The workflow looks like this: question → answer → save as document → open new session → critique document → refinement. By keeping the origin vague, you reduce the model’s tendency to be gentle with its own previous work.
- Works across models. Multiple commenters confirmed this pattern produces strong results on Gemini and Copilot too. It’s not Claude-specific, though the original poster suggests Claude handles self-critique loops especially well.
Why This Pattern Works
The core insight here is that LLMs aren’t just answer machines. They’re reasoning engines. When you give a model permission to revisit and challenge its own output, you’re essentially getting two different “modes” of thinking in one conversation. The first pass generates. The second pass evaluates. Together, they produce something closer to how a careful human expert would work: draft, review, improve.
The best part is how low-effort this is. You don’t need elaborate prompt engineering frameworks. You don’t need system prompts or custom instructions. One sentence after the first response changes the quality of what you get back.
Practical Next Steps
- Try the critique prompt on your very next Claude conversation. Pick something you’ve already asked about and run the loop.
- Experiment with variations: “What did you oversimplify?” or “Where might an expert disagree with you?” can surface different kinds of weaknesses.
- For high-stakes work (strategy docs, technical decisions, research), make the critique loop a default habit. Two rounds minimum.
- Test the “fresh session” technique for anything where you need genuinely unbiased evaluation of a draft.
Want to see the full discussion, including more community variations on this technique? Check out the original thread by u/ReidT205 on r/PromptEngineering.
Frequently Asked Questions
Q: Does this self-critique loop work with other AI models?
Absolutely—users have had great success with Gemini and Copilot using the same pattern. One user tested Copilot and got impressive results when asking it to identify and revise its five weakest assumptions. So it’s not unique to Claude, but Claude does seem particularly tuned for iteration-based workflows.
Q: What’s the simplest way to start using this?
Begin with one of these approaches: ask Claude to summarize its answer again (it’ll often refine it), feed it new information and ask it to reconsider, or ask it to look at the problem from a different angle. Most people see noticeable improvement in clarity and reasoning after just one or two rounds.
Q: What’s the “fresh eyes” technique some people mention?
Extract Claude’s answer into a document, start a completely new session (without mentioning the original source), and ask the fresh session to critique it. Since the new session isn’t anchored to the original reasoning, it can spot weak assumptions that the first session might overlook—basically, it has no bias toward its own work.
Q: How many iterations should I do?
Quality gains are usually biggest in the first two iterations; after that, diminishing returns kick in. The key is being specific about what to improve—”identify your weakest assumptions and strengthen them” gets better results than just “make this better.”
Claude seems unusually good at refining its own answers
by u/ReidT205 in PromptEngineering