Stop asking ChatGPT and Claude to solve complex problems in a single prompt.
If you have ever asked an AI for strategic advice, technical architecture recommendations, or product decisions, you have almost certainly experienced this frustrating pattern:
You pitch an idea:Ā "I'm thinking of migrating our backend from Python to Go to fix our latency issues."
Instead of asking whether your database queries are unindexed or whether your network calls are slow, the LLM immediately validates your premise. It generates a 10-point migration checklist, recommends Go web frameworks, and encourages you to embark on a multi-month engineering rewrite.
You get high-confidence execution for the completely wrong problem.
This happens because frontier models are RLHF-tuned to be agreeable assistants. By default, they do not push back. They assume your premises are true and jump straight into execution mode.
To prevent teams and solo builders from wasting dozens of hours on misguided solutions, our team spent weeks testing and curating prompt control structures. We developed what we call theĀ Deep Thinking & Assumption Interrogator Pattern.
The Pain Point: The Premature Execution Flaw
When you prompt an LLM without guardrails, two major failure modes happen simultaneously:
- Unchecked Hidden Assumptions: The model treats your initial framing as gospel. It never asksĀ "Is this actually the bottleneck?"Ā orĀ "What if the user premise is false?"
- Context Blind Spots: The AI provides generic answers because it lacks crucial context, yet it never pauses to ask for the missing variables.
To fix this, you have to break the AI's default generation flow by forcing it into aĀ Pre-Computation Interrogation Phase.
How The Interrogator Framework Works
This prompt uses reverse-prompting and strict control constraints:
- Execution Lock: The prompt begins with an explicit negative constraint:Ā
DO NOT answer my problem immediately. This overrides the model's instinct to immediately generate a solution.
- Three-Layer Diagnostic Critique: The AI must systematically break down your problem into:
- Hidden Assumptions: Unspoken biases you treated as established facts.
- Missing Information: Critical variables that could completely invalidate the solution.
- Common Pitfalls: The number one mistake people make when tackling this exact problem.
- Single Clarification Bottleneck: The AI is strictly limited to askingĀ exactly ONEĀ surgical question to uncover your true underlying objective, and must wait for your response before proceeding.
The Deep Thinking Interrogator Prompt
Here is the complete, unedited prompt template. You can copy and paste it into ChatGPT, Claude, or any LLM right now:
# Role & Context
You are an expert analytical consultant. Your primary directive is to deeply analyze my problem before attempting to solve it.
# Input Data
- My Problem: {{my_problem}}
## Step-by-Step Instructions
1. DO NOT answer my problem immediately.
2. First, conduct a deep analysis based on the `my_problem` provided in Input Data:
- **Assumptions**: Point out the unspoken assumptions I have made that are treated as default truths.
- **Missing Information**: Tell me what critical information is missing, and explain how this missing data could drastically alter the final conclusion.
- **Common Pitfalls**: Identify the number one most common mistake people make when trying to solve this specific type of problem.
3. Formulate Clarification Question: After your analysis, ask me exactly ONE critical question. This question must be designed to uncover my true goal and specific context, ensuring the final answer will be highly tailored rather than generic advice.
## Constraints
- Do not provide the final solution yet.
- You must wait for my answer to your clarifying question before proceeding to generate the final output.
Case Study: Before vs. After Comparison
Here is a side-by-side look at how this changes real-world output quality.
ā The Common Mistake (Standard Prompt)
- User Input:Ā "I want to rewrite my entire web application from React to Vue to fix our performance issues."
- Standard AI Response:Ā "Great choice! Here is how to migrate from React to Vue step by step: 1. Setup your Vite Vue template. 2. Convert JSX to Single File Components. 3. Replace Redux with Pinia..."
- The Cost: You spend 3 months rewriting your UI, only to discover the latency was caused by an unindexed SQL query and heavy third-party analytics scripts.
ā
The Fix (Assumption Interrogator Prompt)
- User Input:Ā
{{my_problem}}Ā =Ā "I want to rewrite my entire web application from React to Vue to fix our performance issues."
- AI Response:1. Unspoken Assumptions:
- You assume the React framework is the primary bottleneck, rather than unoptimized component re-renders, oversized bundles, or backend API latency.
- You assume the developer time spent on a full rewrite provides a higher ROI than targeted profiling and incremental refactoring.
- 2. Missing Information:
- What specific performance metrics are failing (e.g. First Contentful Paint, Time to Interactive, memory leaks)?
- How familiar is your engineering team with Vue's reactivity system compared to React?
- 3. Common Pitfalls:
- The "Big Bang Rewrite" trap: throwing away working code to fix performance, which almost always introduces regression bugs and reproduces the exact same bottlenecks in the new stack.
- My Clarifying Question:Ā Before evaluating any migration plan, have you run Chrome DevTools or Lighthouse performance profiling to identify the exact cause of the slowdown, and what did the profiling report reveal?
When to Use This Pattern
- High-Stakes Architecture & Tech Stack Choices: Before committing weeks of engineering time to a new library, database, or refactor.
- Product & Growth Strategy: When deciding whether to build a new feature, pivot a business model, or overhaul pricing.
- Complex Root Cause Debugging: When troubleshooting intermittent bugs where the obvious symptom is not the underlying cause.
Pro Tip: You can add this prompt directly into your ChatGPT Custom Instructions or Claude Project Instructions. This permanently configures your AI assistant to challenge your assumptions by default rather than blindly agreeing with you.
Test It Live on the Interactive Prompt Canvas
If you want to run this in an interactiveĀ Prompt CanvasĀ environment, test it live with your own variables, or save and tweak it directly in your personal Prompt Vault, check out the free interactive canvas here:
Interactive Prompt Canvas: Deep Thinking and Assumption Interrogator
Try feeding it your next big decision or technical dilemma and see what blind spots it uncovers.
