TL;DR: One copy-paste prompt makes the model write a short plan before it produces anything. If your request is vague, it asks one clarifying question instead of guessing.
The Problem: Confident Mess
On complex tasks, most of us just paste the request and let the model run. What comes back often looks polished, sounds sure of itself, and is built on the wrong assumptions. A Reddit user in r/PromptEngineering (u/Physical_Number6220) calls this a “confident mess,” and anyone who has used AI for real work knows the feeling.
Picture asking for a landing page for “my small business” and getting back three hundred words of generic copy about a company you never described. You then spend twenty minutes patching it, when two minutes of clarification up front would have fixed it. The model was never told what it didn’t know, so it filled the gaps with guesses.
Their fix is a prompt that forces planning before output.
Breakdown: What the Prompt Actually Does
The prompt has four moving parts.
- A short plan comes first. The model has to state the goal, the constraints it must respect, the steps in order, and the one thing most likely to go wrong. That last item is the sharpest one. Asking for the single biggest risk pushes the model to think about failure before it starts building. For a blog post, that might read: “Risk: the audience isn’t specified, so the tone could miss.” You can spot a gap in about five seconds.
- The clarifying-question escape hatch. If the plan shows the task is underspecified, the model must not produce a final answer. It asks you the single most important clarifying question instead. The original poster says this is the part that saves them, because it stops the model from confidently building the wrong thing on a vague request. A typical question might be: “Who is the reader, and what should they do after finishing this?”
- Execution only when the plan is solid. If the plan holds up, the model runs the steps and delivers the output.
- A one-line constraint check. At the end, the model confirms that each stated constraint was met. It’s a cheap self-audit, and it gives you something concrete to verify. If the check says a constraint was missed, or you spot one it glossed over, reply with that single constraint and ask for a revision.
Why the Single Question Matters
A lot of planning prompts only ask for a plan, and the model then plows ahead no matter what the plan reveals. Here the plan has a job. It acts as a gate. A weak plan stops the process and sends control back to you.
Limiting it to one question is also a smart choice. You don’t get an interrogation. You get the question that unlocks the rest, answer it, and move on. Keep your answer short, a sentence or two is plenty, and the model usually has everything it needs to continue.
Use Cases
- 📝 Long-form writing, where audience, tone, and length decide whether the draft works
- 💻 Coding requests where the stack, existing files, or edge cases weren’t mentioned
- 📊 Reports and analysis where the real question behind the request is fuzzy
- Multi-step workflows, like a campaign outline or a project brief, where one wrong early assumption spoils every step after it
It matters less for simple lookups or quick rewrites. If the task is one step, the plan is overhead.
Prompt of the Day
Here is the prompt as shared by the original poster:
Before producing any output, write a short plan: what is the goal, what are the constraints I must respect, what are the steps in order, and what is the one thing most likely to go wrong here. If the plan reveals the task is underspecified, do not output the final answer, instead ask me the single most important clarifying question. If the plan is solid, proceed: execute the steps and produce the final output, then confirm in one line that each stated constraint was met. Task: [paste]. End prompt.
Replace [paste] with your actual request and send it as is.
A Quick Note on Testing
This post had very little community discussion when I found it, so treat it as a promising technique and not a proven one. The logic is sound, though, and it costs you nothing to try. Run it on your next messy request and compare the result with what you’d normally get. For a fair test, send the same task twice, once plain and once with the prompt, and compare how many rounds of fixes each one needs.
Call to Action
Save this prompt in your notes app, use it on the next task that feels too big to explain in one line, and watch what the model asks you. If the clarifying question is one you hadn’t thought of, the prompt just paid for itself. Tell me how it goes on your own tasks.
A prompt that makes the model plan before it writes a single line
by u/Physical_Number6220 in PromptEngineering