Claude Opus 4.8 has a thinking dial. Most people haven’t touched it.
TL;DR: On max effort mode, Claude stops agreeing with you and starts finding holes in your logic. One prompt structure does this reliably, and it’s already caught two genuine mistakes for the person who built it.
What effort control actually changes
Default Claude is agreeable. You say you’re leaning toward X, it helps you with X.
Max effort Claude is different. It reasons through multiple approaches before responding. More importantly, it tells you where it’s uncertain instead of just confirming what you already believe.
Think about what that means in practice. You’re considering a pricing change. You explain your reasoning, and standard Claude walks you through how to implement it. Max effort Claude might come back and say: “Your assumption that users will stay at the higher price point depends on retention data you haven’t mentioned. If churn is above a certain threshold, this math breaks.” That’s not a detail standard mode skips on purpose. It’s just how agreeable defaults work. The model optimizes for being helpful in the direction you’re pointing.
That’s a small toggle with a real practical difference. Extended thinking existed before. What Opus 4.8 changes is how cleanly you can invoke it, and how much it shifts the quality of the output when you do. The threshold between “Claude helping you execute a plan” and “Claude auditing whether the plan is sound” is now a single line in your prompt.
The prompt structure
This comes from a r/PromptEngineering thread. The key insight is that it forces Claude into decision-review mode, not thinking-out-loud mode:
Maximum effort on this. Don’t rush it.
I’m deciding: [the decision]
I’m leaning toward: [your option] because [reasons]Argue against me first. What am I not seeing?
What assumption am I making that, if wrong, changes everything?
Tell me where you’re certain and where you’re not.Then your honest call: proceed, reconsider, or get more info.
Three things make this work:
- It asks Claude to argue against you first, not just think more
- It separates certainty from uncertainty explicitly
- It ends with a forced call, not a summary
That last one is underrated. “Here’s what I found” is filler. “Reconsider” is something you can act on.
The “argue against me first” instruction is doing the heaviest lifting here. Without it, Claude naturally builds on your framing. With it, you’re telling the model to treat your reasoning as a hypothesis to stress-test, not a direction to follow. That’s a fundamentally different task, and the output reflects it. In the original thread, the two real mistakes it caught were both cases where the person had already decided. The logic felt solid. The prompt found the crack anyway.
The uncertainty line matters too. Most AI responses either sound confident across the board or hedge everything equally. Asking Claude to separate what it knows from what it’s guessing forces a more honest structure. You walk away knowing which parts of the response to verify and which parts to trust.
🎯 Use Cases
- Any business decision you’ve already half-made
- Pricing or positioning changes before they go live
- Hiring or partnership calls where you’re leaning yes
- Anything where your own confirmation bias is the actual risk
- Technical architecture choices where switching costs are high
- Contract or deal terms you’re about to sign without a second opinion
Prompt of the Day
Copy this. Drop in your real decision. Run it on max effort in Opus 4.8.
Maximum effort on this. Don’t rush it.
I’m deciding: [the decision]
I’m leaning toward: [your option] because [reasons]Argue against me first. What am I not seeing?
What assumption am I making that, if wrong, changes everything?
Tell me where you’re certain and where you’re not.Then your honest call: proceed, reconsider, or get more info.
Five minutes. Before any decision that actually matters.
Worth trying today
Pick something you’ve already decided. Something you’re pretty sure about. Run this prompt before you commit.
The people who get the most out of this use it as a pre-mortem. Not “what could go wrong” in the abstract, but “here’s the specific decision I’m about to make, here’s why I think it’s right, now tell me where I’m wrong.” That specificity is what makes the output useful instead of generic.
You either get confirmation you’re on the right track, or you find the hole you were about to walk into. Both outcomes are worth five minutes. And if it comes back with “proceed,” you move forward with more confidence than you started with. That’s not nothing either.
Frequently Asked Questions
Q: What’s the difference between just asking Claude to think harder and this structured approach?
Just cranking up effort gets you longer text, not necessarily better decisions. The real difference is the structure: ask Claude to argue against you, name the assumption that would change everything, separate where it’s certain from where it’s guessing, and end with a clear call (proceed/reconsider/get more info). That last part, the decision gate, prevents Claude from rambling and actually forces a judgment.
Q: When should I actually use Max effort?
Use it on decisions where you’d actually regret being wrong, hiring, big purchases, strategy shifts, partnerships. For routine choices between familiar options, normal Claude is fine. Max effort is about preventing the kind of mistake that sticks with you, not about over-analyzing everything.
Q: Why does separating certainty from uncertainty matter?
It shows you where the real risk lives. If Claude says it’s confident in the timeline but then admits it’s guessing about adoption rates, and adoption is what actually drives the timeline, that’s a red flag. You can’t manage risk you don’t see.
Q: What does “naming the assumption that would change everything” actually mean?
Every decision rests on invisible assumptions, about costs, timing, how people will respond, what competitors will do. Asking Claude “What if this assumption is wrong?” surfaces the biggest one. Half the value is realizing it exists. The other half is asking yourself: have I actually validated that, or am I just hoping it’s true?
The new Claude lets you tell it how hard to think. I run this on every important decision now and it’s caught two mistakes I was about to make.
by u/Professional-Rest138 in PromptEngineering