Before you pitch your idea to anyone, pitch it to a hostile AI first. The rejection reasons you get back will save you more grief than a thousand “great idea” replies.
Most people use AI as a yes-machine. You describe your plan, it tells you what’s solid, and you walk away feeling validated. That’s not feedback. That’s a mirror. A contributor in r/PromptEngineering shared a single technique that breaks that pattern, and the community response was immediate: everyone should be doing this.
What the Adversarial Prompt Does
Instead of asking AI to help you build your case, you ask it to destroy it. The approach works because it surfaces objections you’re too close to see yourself. When you’re the one who built the idea, you have a natural blind spot for the weaknesses. You’ve been living with the concept long enough that the gaps start to look like features. A hostile reviewer doesn’t share that blind spot.
The cynical VC angle is particularly effective. Venture capitalists have seen thousands of pitches fail. They’re trained to find the gap between what founders believe and what the market will actually do. Assigning that role to the AI gives the model a specific, credible skeptic frame to work from. It also forces the model to prioritize fatal flaws over surface suggestions, which is exactly what you need.
The Prompt
Here’s the exact prompt the original poster shared:
“Here is my business plan. Act as a cynical venture capitalist. Give me 5 reasons why you would REJECT this deal.”
That’s the whole thing. Paste in your plan, get back a stress test. A few elements make it work:
- 🎯 Role assignment: “cynical venture capitalist” sets a specific skeptic persona with built-in domain expertise
- Hard number: “5 reasons” forces the model past the obvious first objection and into the uncomfortable second and third ones. The first two objections are usually things you already know. The fourth and fifth are where the real problems live.
- Capital letters on REJECT: removes ambiguity about what kind of feedback you want. The model won’t hedge into “here are some areas to consider improving.”
The capitalization trick is worth noting separately. Language models respond to emphasis. Saying REJECT instead of reject signals that you want direct criticism, not diplomatic suggestions wrapped in encouragement. It’s a small thing that consistently produces sharper output.
Use Cases Beyond Business Plans
The same adversarial logic applies to almost anything you’re about to commit time or money to.
- Product feature: “Act as a frustrated user. Give me 5 reasons this feature would annoy you.”
- Marketing copy: “Act as a skeptical customer who’s seen too many ads. Give me 5 reasons this headline would make you scroll past.”
- Job application: “Act as a hiring manager with 200 resumes on your desk. Give me 5 reasons you’d skip this one.”
- Content strategy: “Act as an editor who’s read everything. Give me 5 reasons this topic doesn’t need another article.”
- Pricing decision: “Act as a price-sensitive buyer. Give me 5 reasons this price would make me walk.”
The pattern holds across all of them: assign a skeptical role with a real reason to say no, state the ask clearly, demand a specific number of objections. The role you choose matters more than most people realize. A frustrated user and a skeptical investor will find completely different holes in the same plan. Run it through both if the stakes are high enough.
Prompt of the Day
“Here is my [business plan / product idea / marketing copy / strategy]. Act as a cynical [venture capitalist / customer / competitor / expert]. Give me 5 reasons why you would REJECT or dismiss this.”
Swap in whatever role fits the context. The key is picking someone with genuine incentive to say no, not someone who’d politely suggest improvements. A mentor is useful. A cynical competitor is more useful for this particular exercise.
How to Use the Results
The objections AI returns aren’t always right. Some will be generic. A few might miss the specifics of your situation. That’s fine. The point isn’t a definitive verdict. It’s to force yourself to have clear answers before the real conversation happens.
If an objection stings a little, that’s usually a sign it deserves a direct response in your plan. If you can answer it easily, great. If you can’t, the gap is real and it’s better to know now.
One iteration that works well: run the adversarial prompt, write rebuttals to each rejection reason, then ask the AI to evaluate whether your rebuttals hold up. You’re essentially running a pre-mortem and then patching the holes before anyone else sees the plan. If your rebuttal doesn’t satisfy the skeptic persona, it probably won’t satisfy a real investor or customer either. Keep tightening until the answers are clean.
Head over to the original thread in r/PromptEngineering to see how others in the community are adapting this technique across different contexts.
Frequently Asked Questions
Q: Why should I spend time tearing my idea apart if it feels solid?
The best idea doesn’t always win. What matters is not stepping on landmines (critical mistakes), which kill ideas way more often than weak concepts do. A mediocre idea executed well beats a brilliant idea executed carelessly; you’re just finding the traps before you hit them.
Q: Won’t listing all the ways my idea could fail just depress me and make me paralyzed?
Feels that way at first, but hiding from problems doesn’t make them disappear. It just means you’ll hit them unprepared. The emotional discomfort is temporary and productive. Once you see the problems, you can prioritize which ones matter, and the feeling goes from “this is impossible” to “okay, here’s my plan.”
Q: How is asking an AI to reject my idea different from just thinking through the downsides myself?
You’re already good at spotting some problems, but you’re also naturally protective of your own ideas. That’s just human nature. An AI playing a cynical outsider removes that emotional filter and spots blind spots you’d miss faster than doing it alone.
Q: When should I do this? Is it just for major business decisions?
Everything: a product plan, a new feature, picking a restaurant, a job offer. Anywhere you’re making a decision that matters, ask yourself (or an AI) for the five reasons not to do it. Once you make it a habit, you stop stepping on landmines.
The ‘Adversarial Prompt’: Testing your own logic.
by u/Significant-Strike40 in PromptEngineering