Rephrase and Respond (RaR) — Prompting Guide & Examples
Rephrase and Respond asks the AI to first rephrase the user's question in its own words before answering. This simple step forces the model to deeply process the question, resolve ambiguities, and often reveals the true intent — leading to more accurate and relevant answers.
How It Works
Add an instruction: 'First, rephrase my question to make sure you understand it correctly. Then answer the rephrased version.' The model's rephrasing reveals how it interprets the question, and answering its own clear version produces better results.
When to Use
Use RaR for ambiguous questions, complex multi-part queries, and when you've noticed the model misunderstanding your intent. Also useful for customer support bots and chatbots where user queries are often unclear.
Model-Specific Tips
ChatGPT / GPT-4
GPT-4 handles RaR well. Add 'First rephrase, then answer' to your prompt. The rephrasing often catches ambiguities the model would otherwise guess at.
Claude
Claude excels at RaR — it naturally tends toward clarification. Ask Claude to restate the question before answering for more precise responses.
Gemini
Gemini supports RaR prompting. The rephrasing step helps Gemini focus on the most relevant aspects of complex queries.
Pros & Cons
Pros
- ✓ Catches misunderstandings before they propagate
- ✓ Forces deeper processing of the question
- ✓ Simple — just add one instruction
- ✓ Great for ambiguous or complex queries
Cons
- ✗ Adds a small amount of extra output
- ✗ Can feel redundant for clear questions
- ✗ Rephrasing may occasionally shift intent
- ✗ Slight latency increase
Example Prompts
First, rephrase my question to make sure you understand it. Then answer your rephrased version. Question: How do I make my website faster when it's slow because of images and too many API calls and the database is also slow?
Before responding, restate my request in your own words to confirm understanding. Then provide your response. Request: I need something that shows our team how the project is going with the budget and timeline and risks, like a dashboard but not too complicated.
Step 1: Rephrase this question more precisely. Step 2: Answer the precise version. Question: What's the best way to handle state in a big React app with lots of forms and API data and real-time updates?