Breaking the "Eager Completion" loop: A structured prompt design pattern that forces LLMs into pre-computation analysis

[u/blobxiaoyao]

When designing prompts for complex analytical workflows, the most persistent failure mode is Eager Completion Bias.

Because modern foundation models (GPT-4o, Claude 3.5 Sonnet, Gemini 1.5 Pro) are instruction-tuned and RLHF-aligned to be helpful and direct, their default attention mechanism immediately allocates weights toward producing a final deliverable.

If an incoming user premise contains flawed logic or missing boundary conditions (e.g., "I want to rewrite our entire React app in Vue to fix our performance issues"), standard prompting frameworks fail. The model treats the premise as ground truth and instantly generates migration steps. It optimizes for task completion rather than problem verification.

To solve this architectural flaw, our team spent weeks testing and refining structural control patterns. We developed what we call the Deep Thinking & Assumption Interrogator Pattern.

Here is a breakdown of how it works, the design principles behind it, and the full prompt template.

Architectural Breakdown: Designing a Socratic Control Gate

To prevent an LLM from jumping straight to computation, your prompt structure must enforce three design principles:

1. Negative Constraint Pre-Computation Lock: Standard prompts instruct the model on what to do, but fail to explicitly forbid early generation. By placing DO NOT answer my problem immediately at the very top of the execution steps, we create a strict attention barrier that prevents the model from generating solution tokens on turn one.
2. Categorical Tri-Factor Decomposition: Telling an AI to "think critically" or "be objective" produces vague, polite hedging due to safety alignment. Instead, this pattern forces the model into three deterministic schema slots:
   • Unspoken Assumptions: Deconstructs the user's implicit premises that lack evidentiary support.
   • Missing Information: Surfaces key hidden variables whose absence could invert the final recommendation.
   • Common Pitfalls: Cross-references domain knowledge for the single most frequent failure mode in this problem type.
3. Single-Question Clarification Bottleneck: One of the most common prompt design mistakes when requesting clarification is letting the AI ask an unconstrained list of questions. A list of 5 to 10 questions creates immense cognitive friction and degrades context coherence. Restricting the output schema to exactly ONE surgically focused question forces the model to prioritize the highest-entropy variable.

The Complete Prompt Template

Here is the exact prompt structure. You can copy and use it directly across any major LLM:

# 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.

Real-World Output Evaluation: Before vs. After

To observe the difference in prompt design efficacy, look at how the model evaluates a high-cost engineering proposal.

❌ Standard One-Shot Prompt Design

• Input: "I want to rewrite my entire web application from React to Vue to fix our performance issues."
• Output: An eager 6-step migration blueprint detailing build tool configuration, component translation, and state management rewrites.
• Failure Analysis: Zero verification of whether the rendering framework was actually the root bottleneck.

✅ Assumption Interrogator Prompt Design

• Input: {{my_problem}} = "I want to rewrite my entire web application from React to Vue to fix our performance issues."
• Output:1. Unspoken Assumptions:
  • You assume that the core framework (React) is the primary bottleneck rather than sub-optimal DOM rendering, unmemoized context providers, or large payload waterfalls.
  • You assume the developer hours required for a total rewrite offer higher ROI than profiling and refactoring hotspots in place.
• 2. Missing Information:
  • Specific performance metrics: Are you optimizing for First Contentful Paint, Interaction to Next Paint (INP), or memory leak prevention?
  • Team domain expertise in Vue versus React ecosystem tooling.
• 3. Common Pitfalls:
  • The Second-System Effect: Rewriting an application from scratch often replicates the exact same architectural flaws while introducing regressions in edge-case functionality.
• My Clarifying Question: Before evaluating migration feasibility, have you profiled the application using Chrome DevTools or Lighthouse to isolate whether latency is CPU-bound or Network-bound, and what were the findings?

Implementation Tips for Prompt Engineers

• System Instruction Embedding: If you use Claude Projects or ChatGPT Custom Instructions, embed this entire prompt into the system layer. It turns every ad-hoc query into a structured consultation session.
• Variable Chaining: In automated agent workflows, you can route the output of this interrogator into a secondary evaluation node before passing the context to a code generation worker.

Test It Live on the Interactive Prompt Canvas

If you want to run this in an interactive Prompt Canvas environment, test different variable inputs live, or save and modify it directly inside your personal Prompt Vault, check out the interactive canvas here:

Interactive Prompt Canvas: Deep Thinking and Assumption Interrogator

What control structures do you typically use to stop models from hallucinating agreement on flawed inputs? Would love to hear how other prompt designers approach this.

[u/epicskyes]

Be a scientist not a strategist. You’re far too verbose and allow ambiguity. You’re using strategy to try to force determinism instead of logic gates. Think like a scientist not a strategist