Back to cookbook

AI Prompt for Self-Critique and Refinement Before a Final Answer

19 views Published

Make this prompt yours

Share

This AI prompt for self-critique and refinement is for anyone who wants a model to check its own draft answer for gaps, errors, or unsupported claims before presenting it as final β€” a technique sometimes called self-reflection or reflexion prompting. It's aimed at tasks where a first-pass answer is often good but not quite reliable enough to use as-is: analysis, technical explanations, plans, and written drafts where a second look tends to catch something the first pass missed.

The prompt works by making the model produce a draft, then explicitly evaluate that draft against a checklist (accuracy, completeness, unsupported assumptions, clarity) before writing a revised version. Separating drafting from critique matters because a model asked to "double-check your answer" in the same breath as the original question often just restates it with more confidence rather than genuinely re-examining it.

For prompts you'll reuse regularly where the stakes of a missed error are higher β€” a system prompt, an agent instruction set, or a prompt driving an automated pipeline β€” running it through Prompt Debugger first catches the vague constraints and edge cases that a single self-critique pass on one output won't fix at the source.

Prompt template

Make this prompt yours

prompt-template
240 tokens
Role: You are an assistant that produces a draft answer, critiques it against explicit criteria, and then revises it. Context: - Task or question: [THE ACTUAL TASK OR QUESTION TO ANSWER] - Relevant background or constraints: [ANY FACTS, RULES, OR LIMITS THE ANSWER MUST RESPECT] - Critique criteria: [E.G. FACTUAL ACCURACY, COMPLETENESS, UNSUPPORTED ASSUMPTIONS, CLARITY] Instructions: 1. Write a first draft answer to the task above. 2. Critique the draft explicitly against each criterion listed. For each one, state whether the draft passes or has an issue, and describe the issue if there is one. 3. Write a revised final answer that addresses every issue found in step 2. Constraints: - Do not skip stating an issue just because it would require significant rework - Do not present the draft and the revision as identical if real issues were found - If no issues are found for a criterion, say so explicitly rather than omitting it Output format: 1. Draft Answer 2. Critique (one line per criterion) 3. Revised Final Answer

Want it sharper? Optimize this prompt with Prompt Optimizer, check it with the Prompt Debugger or shorten it with the Token Optimizer.

Example input

example-input
145 tokens
Role: You are an assistant that produces a draft answer, critiques it against explicit criteria, and then revises it. Context: - Task or question: Write a short recommendation on whether a small e-commerce business should migrate from a monolithic app to microservices - Relevant background or constraints: The business has 3 backend engineers total and currently handles about 2,000 orders per day - Critique criteria: Factual accuracy, completeness, unsupported assumptions, clarity Instructions: 1. Write a first draft answer. 2. Critique the draft against each criterion. 3. Write a revised final answer addressing every issue found. Output format: 1. Draft Answer 2. Critique 3. Revised Final Answer

When to use it

  • Getting an analysis, recommendation, or technical explanation where a first draft often misses edge cases
  • Reviewing a written draft (email, report, summary) for factual gaps or overstated claims before sending it
  • Working through a multi-step reasoning problem where an early mistake would compound
  • Generating content for a high-stakes use case where a second, explicit check is worth the extra step

Best practices

  • Give the model a concrete checklist to critique against (accuracy, completeness, assumptions, clarity) rather than a vague "check your work"
  • Ask it to list specific issues found in the draft before writing the revision, not just produce a revised answer silently
  • Use this for genuinely uncertain or complex tasks β€” running it on simple factual questions mostly just adds latency
  • For a prompt you'll run repeatedly rather than a one-off answer, fix the underlying instructions at the source instead of relying on self-critique every single run

Common mistakes

  • Asking the model to "double check" in the same turn as the original question, which often just re-confirms the same answer
  • Treating the self-critique step as proof the final answer is correct rather than as one useful signal among several
  • Not giving specific criteria to critique against, which produces a vague "looks good" instead of real scrutiny
  • Using this technique for simple, low-stakes questions where it adds delay without meaningfully improving accuracy

FAQs

What is a self-critique or reflexion prompt?

It's a prompting technique where the model is asked to produce a draft answer, evaluate that draft against explicit criteria, and then write a revised answer addressing what it found. Separating the drafting and critique steps produces more genuine scrutiny than simply asking the model to double-check its answer.

Does asking an AI to double-check its answer actually improve accuracy?

Asking in the same turn, without explicit criteria or a separate critique step, often just produces a more confident restatement of the same answer rather than real re-examination. Structuring the request as distinct draft, critique, and revision steps against named criteria is what tends to surface real issues.

When should I use self-critique prompting versus just asking directly?

It's most useful for genuinely complex or uncertain tasks β€” analysis, multi-step reasoning, technical recommendations, high-stakes written drafts β€” where a second look plausibly catches something real. For simple factual questions it mostly adds latency without meaningfully changing the answer.

Can this technique catch factual errors, or only structural or reasoning issues?

It can catch some factual errors, especially internal inconsistencies or unsupported claims within the draft itself, but it can't verify facts against a source it wasn't given. For claims that need to be checked against real data or documents, pair this technique with retrieval or a human review step rather than relying on self-critique alone.

Which Cuelara tool can help me build a stronger version of this prompt?

Prompt Debugger β€” it scans a prompt for vague constraints, logical loopholes, and edge cases before you run it, which is especially useful for a reusable self-critique prompt where a weak criterion undermines every run built on it.

Found this prompt useful? Share it.

Share

More in Prompt Fundamentals & Techniques

Prompt Fundamentals & Techniques

AI Prompt for Analogical Prompting to Generate Self-Created Examples Before Answering

Analogical prompting is a technique where, instead of you writing few shot examples by hand, you ask the model to first recall or invent sim…

You are solving a problem using analogical reasoning.

STEP 1: Before solving the problem below, recall or generate 2 related problems that share a similar underlying structure or reasoning pattern. For each one, briefly state the problem and how it would be solved.

STEP 2: Identify what reasoning approach or pattern those examples have in common.

STEP 3: Apply that same reasoning approach to solve the actual problem below. Show your work step by step.

ACTUAL PROBLEM:
[YOUR QUESTION OR PROBLEM HERE]

OUTPUT FORMAT:
- Related Examples: (2 short examples with solutions)
- Shared Pattern: (1-2 sentences)
- Final Answer: (clearly labeled, with step-by-step reasoning for the actual problem)

Make this prompt yours

Prompt Fundamentals & Techniques

AI Prompt for Multi-Persona Debate to Stress-Test an Idea

Multi persona debate prompting is a technique where you ask a model to argue a decision or idea from several distinct, opposing viewpoints b…

You are facilitating a structured debate between multiple expert personas to help evaluate a decision.

DECISION TO EVALUATE:
[DESCRIBE THE DECISION OR IDEA, e.g. "Should we raise our subscription price by 20% for new customers?"]

CONTEXT:
[RELEVANT BACKGROUND: company size, current numbers, constraints, timeline]

PERSONAS:
1. [PERSONA 1 β€” e.g. "Risk-Averse CFO who prioritizes cash flow stability and customer retention"]
2. [PERSONA 2 β€” e.g. "Aggressive Growth Lead who prioritizes revenue growth and market share"]
3. [PERSONA 3 β€” e.g. "Customer Success Manager who prioritizes existing customer satisfaction"]

TASK:
1. Have each persona give a 2-3 sentence opening argument from their specific incentive and priorities
2. Run one round of rebuttal where each persona directly challenges at least one point from another persona
3. After the debate, provide a neutral synthesis that lists the strongest point from each side
4. End with a short, clearly labeled recommendation and the key risk to monitor if that recommendation is followed

CONSTRAINTS:
- Keep each persona's arguments distinct and grounded in their stated priorities, not generic pros/cons
- Do not let the synthesis simply average the positions β€” it should make an actual call
- Flag any assumption the personas are relying on that isn't confirmed in the context provided

OUTPUT FORMAT:
Label each section clearly: Opening Arguments, Rebuttals, Synthesis, Recommendation.

Make this prompt yours

Prompt Fundamentals & Techniques

AI Prompt for Step-Back Prompting to Improve Reasoning Accuracy

Step back prompting is a technique for getting more accurate answers from ChatGPT, Claude, or Gemini by asking the model to first state the…

ROLE: You are a careful reasoning assistant that solves problems by first identifying general principles.

TASK: Answer the following specific question: [SPECIFIC QUESTION OR PROBLEM]

CONSTRAINTS:
1. Before answering, state the general principle, rule, or concept that applies to this type of problem. Write this as a standalone statement that would be true for any similar problem, not just this one.
2. Then explain how that general principle applies to the specific details given.
3. Only after steps 1 and 2, give your final answer.
4. If your final answer seems to contradict the general principle you stated, flag the contradiction and revise instead of ignoring it.

OUTPUT FORMAT:
General Principle: [the abstracted rule]
Application: [how the rule applies to this specific case]
Final Answer: [the specific answer]

DOMAIN CONTEXT: [OPTIONAL: SUBJECT AREA, E.G. PHYSICS, TAX LAW, SOFTWARE DEBUGGING]

Make this prompt yours