The Reversal of Perspective

Put your original prompt into a tag - <my_prompt> - and ask for the interpretation as a separate, structured task. That framing stops it from quietly producing an improved answer instead of a diagnosis. Claude is also comfortable being asked to show its reasoning before its conclusion, so ask for every reading it considered and the one it chose, in that order: the readings it rejected are often where your real ambiguity is hiding. Tell it explicitly not to be diplomatic about it.

• Put the original prompt in a tag and ask about it.
• Ask for all readings considered, then the chosen one.
• Say "do not take the blame" - it will otherwise.
• Ask what it would have advised rather than followed.
• Treat the answer as a second reader, not a log.

**Message 1 - the reversal**

<my_prompt>
Write a social media post about our company's new charity initiative. We need to get this out there and be very professional and buttoned-up about it.
</my_prompt>

<task>
Diagnose the prompt above. Do not write a better post - I will ask for that next.
</task>

<questions>
1. What tone and style did you understand this to be asking for? Quote the specific words that told you.
2. What other readings of "professional and buttoned-up" were available, and why did you choose the one you did?
3. Given that this is a charity initiative going on social media, what do you think I actually wanted? Where does that conflict with what I wrote?
4. Is there an internal contradiction here - between getting something shared widely and keeping it buttoned-up?
</questions>

<tone_of_your_reply>
Direct. Do not apologise, do not take the blame, and do not tell me the prompt was reasonable. I wrote a flawed instruction and I want the flawed word named. Diplomacy here costs me the lesson.
</tone_of_your_reply>

---

**Message 2 - the corrected prompt**

<context>
My first attempt failed because I wrote "professional and buttoned-up" when I meant "not flippant". It was read as "corporate", which is the one register in which nobody shares anything.
</context>

<task>
Write a social media post about our new charity initiative.
</task>

<tone>
Inspiring and warm. Not corporate. No "we are pleased to announce". Someone scrolling past should feel something and want to pass it on.
</tone>

<goal>
A reader feels good about the brand and shares the news. This is not a formal record of the announcement.
</goal>

<constraints>
- Lead with the people it helps, not with our company.
- Short enough to read without tapping "more".
- One clear line on how to get involved.
</constraints>

<format>
Three versions at increasing levels of warmth, so I can see the range. I do not yet know where my own line sits, and three drafts will tell me faster than another round of adjectives.
</format>

**Message 1 - the reversal**

<my_prompt>
I need a plan to improve the velocity of my engineering team.
</my_prompt>

<task>
Do not revise the plan. Tell me what my prompt communicated.
</task>

<questions>
1. What did you take "velocity" to mean here? List every reading you considered - not only the one you used.
2. Which did you choose, and what in my sentence decided it?
3. Was there anything in my prompt that could have told you whether I meant the Agile sprint metric, general delivery speed, or something looser about momentum and morale?
4. What else was underspecified that mattered more than the word velocity?
</questions>

<how_to_handle_uncertainty>
If my prompt genuinely did not contain enough to choose between readings, say that plainly rather than reverse-engineering a justification for the one you picked. "There was no way to know" is the most useful possible answer here.
</how_to_handle_uncertainty>

<tone_of_your_reply>
Do not blame yourself. I am asking what my sentence actually said to a reader outside my company.
</tone_of_your_reply>

---

**Message 2 - the corrected prompt**

<definition>
Velocity here means the Agile metric: story points completed per two-week sprint. Not general speed, not morale.
</definition>

<context>
[Team size] engineers. Currently averaging [X] points per sprint; target [Y]. The complaints I hear internally are [the real bottleneck - code review queues, unclear requirements, interruptions, flaky tests].
</context>

<task>
A plan to improve sprint velocity, separated into three parts.
</task>

<format>
1. Changes that genuinely increase throughput.
2. Changes that only inflate the number - looser estimation, splitting tickets, counting differently. Name these explicitly so I can avoid them. They are the easiest way to hit my target while learning nothing, and I would rather see them labelled than stumble into them.
3. What to measure alongside velocity so I notice if quality is paying for the speed.
</format>

<before_you_start>
If velocity is the wrong thing to optimise given the bottleneck I described, say so first and say why. A competent plan for the wrong goal is worse than an argument about the goal - and given that this whole exchange started with me using an ambiguous word, I would rather have the argument.
</before_you_start>

**Message 1 - the reversal**

<my_prompt>
I am giving a presentation to a potential client in Hyderabad. They are a big construction company. My company sells advanced drone-based surveying equipment. The presentation needs to include all the technical specs of our top three drone models. Create an outline.
</my_prompt>

<task>
Diagnose this. Note first that it is not a vague prompt - it is detailed and specific, and the outline it produced still was not persuasive. That is what I want explained.
</task>

<questions>
1. What did you understand the single most important goal of this presentation to be? One sentence, as you inferred it.
2. Which part of my prompt put that goal there?
3. Here is the real question. If you were advising me rather than following my instruction, what would you say the goal of a first meeting with a potential client is? Where does that differ from the goal my prompt specified?
4. Why would adding more detail to my prompt not have fixed this?
</questions>

<tone_of_your_reply>
Blunt. My prompt was specific, so I assumed it was good. Tell me what it specified that it should not have, and do not soften it.
</tone_of_your_reply>

---

**Message 2 - the corrected prompt**

<primary_goal>
Persuade a major construction client in Hyderabad to book a live demonstration. One outcome; nothing else matters as much.
</primary_goal>

<context>
My company sells drone-based surveying equipment. The audience is a large construction company - probably project managers plus someone from finance.
</context>

<task>
A persuasive presentation outline built on benefits, not features.
</task>

<requirements>
- Frame everything as what a traditional survey currently costs them in days of delay, rupees and safety risk - not as what our drones can do.
- Time saved, cost reduced, safety improved on large construction sites.
- Technical specifications: one appendix slide, referenced only if asked.
- Per slide: the single message it must land, and the question it should leave the audience wanting to ask.
- Close with a specific ask for the demonstration - a date, a site, a named person.
</requirements>

<before_the_outline>
Tell me the one thing I have still not given you that would most improve this. I have now been wrong once about what mattered in this brief, so I am not assuming I have got it right the second time either.
</before_the_outline>