TL;DR: Most AI feedback is just validation with a disclaimer at the end. This prompt skips that and goes straight for the thing you shouldn’t be trusting.
Why Default Feedback Falls Flat
Claude wants to be helpful. That usually means leading with what’s working, softening the critique, and leaving you feeling better than you should.
That’s a problem when you’re making a real decision.
The default output sounds like: “This is a solid approach. A few things worth considering…” And then you read those considerations, nod, and do nothing with them.
It’s not that the feedback is wrong. It’s that the framing is designed to preserve the relationship, not to help you avoid a costly mistake. The AI is pattern-matching to “helpful assistant” when what you actually need is someone willing to say the hard thing first. If you ask for a review, you get a review. If you ask for encouragement with a side of caution, that’s what you get. The prompt design is doing more work than you realize.
Think about the last time you got feedback from a colleague before a big pitch. If they started with “this is really strong,” you probably relaxed. And everything after that landed softer because of it. That’s how priming works, and AI does the same thing. The way you frame the question shapes the answer you receive, almost completely.
What This Prompt Does Differently
It flips the framing entirely.
Instead of asking for a review, you’re asking for a smart friend who already suspects you’ve missed something. The instruction is explicit: don’t start with what’s good. Start with what gives you pause.
That’s a completely different conversation.
The three questions it forces out are sharp:
- 🎯 The assumption you’re most confident about (the one most worth challenging)
- The scenario where your whole argument collapses
- What a smart opponent would say that you’d actually have to sit with
Notice what’s missing: “strengths,” “good points,” “solid foundation.” None of that.
Each question is doing specific work. The first one targets your blind spot, not your weak spot. Weak spots are things you already know are risky. Blind spots are things you’ve stopped questioning because you’ve thought about them so many times they feel obvious. The second question stress-tests the logic under pressure, forcing you to name the exact conditions where you’re wrong. The third one is the one that stings: it asks for the argument that would actually make you pause, not just a generic objection. That’s a lot harder to dismiss.
Together, they give you the kind of feedback a good advisor would give you if they had no incentive to be polite about it.
Where to Use It
- Business decisions before you commit budget
- Strategies before you pitch them to a team
- Arguments before you publish
- Any plan where you’re already pretty sure you’re right
That last one is the key. The more certain you feel, the more useful this prompt gets.
Budget decisions are the obvious place to start. Before you sign off on a spend, run your logic through this and see if the core assumption holds. If you’re betting on a market behaving a certain way, or a channel performing above average, that’s exactly the kind of thing this prompt will surface.
For pitches and presentations, the timing matters. Run it the day before, not the morning of. You want enough time to actually do something with what comes back. If the output reveals a gap in your argument, you need runway to close it, not just a tense hour before you go live.
For published arguments, this is your last check before you put something out in public that people can respond to. A strong objection, caught early, can push your thinking forward. A weak assumption, published prematurely, can undercut everything else you’ve built around it.
🗓️ Prompt of the Day
Read what I've written below like you're a smart friend who genuinely thinks I might be wrong about something important. Don't start with what's good. Start with the thing that gives you the most pause. Then tell me: 1. The assumption I'm most confident about that you'd want me to pressure-test 2. The scenario where my reasoning completely breaks down 3. What someone who strongly disagrees with me would say that I'd actually have to think about Don't soften it. I'd rather know now. Here's what I'm thinking: [paste]
The Part That Actually Earns It
That first question is the one. “The assumption you’re most confident about” is almost always the load-bearing belief nobody thought to test.
Most failed plans don’t fall apart on the edges. They fall apart at the center, on the thing everyone assumed was solid and nobody questioned.
The startup that was certain their target customer wanted the product. The campaign built on the assumption that a certain channel would convert. The strategy predicated on a competitor staying still while you moved. These aren’t edge cases. They’re the norm. The assumption felt obvious at the time. That’s exactly why it never got tested.
There’s something worth sitting with here: the stronger your conviction, the more dangerous the assumption underneath it. High confidence isn’t a signal that you’ve thought something through carefully. Sometimes it’s a signal that you stopped thinking about it a long time ago and just started defending it.
This prompt forces a reset. It asks you to step back from defending and start interrogating, just for a moment, the thing you’d least want to be wrong about.
Try it on the next decision you’re already sure about. That’s exactly when it hits hardest.
Want more prompts like this? We drop the best ones every week in the Cyber Corsairs newsletter. Join the crew.
The most useful thing I’ve changed about how I use Claude: I ask it to read my thinking like a smart friend who suspects I’m wrong.
by u/Professional-Rest138 in PromptEngineering