Most people open a chat window, type one tight instruction, and then spend twenty minutes fixing what comes back. A Redditor in r/PromptEngineering described a different habit. They stopped writing prompts and started briefing the AI like a colleague. Then they asked the AI to write the prompt for them.
The Key Idea
Instead of squeezing your request into one clever line, you talk. You explain what you’re building, what the goal is, what result you want, and where you keep getting stuck. You keep going until you’ve run out of things to say. Only then do you ask: “Based on all that, write me the best prompt to get this done.”
You run that prompt, and the output is usually far closer to what you pictured.
One commenter pointed out that this is still prompting. That’s fair, and it’s true. But it’s prompting where the AI does the part it’s good at (structuring instructions) and you do the part only you can do (knowing what you actually want).
Think about how you’d work with a new freelancer. You wouldn’t hand them a single sentence and walk away. You’d tell them about the client, the deadline, the last time something went wrong, and the style you like. The freelancer would then turn that conversation into a clear plan. That’s exactly the split here. You supply the knowledge, the AI supplies the structure.
Old Way vs. New Way
The old way: You write a short, polished prompt from memory. You leave out context because it feels obvious to you. The AI fills the gaps with generic guesses. You tweak the wording again and again, hoping the right phrase unlocks it.
The new way: You dump the full context first. The AI sees your constraints, your worries and your definition of “good.” It then turns that mess into a clean, structured prompt that includes details you would never have thought to write down.
The difference is where the effort goes. The old way spends it on phrasing. The new way spends it on clarity. Clarity is the part that actually moves the result.
Here’s a quick example. Say you want a product description for a handmade candle shop. The old way gives you: “Write a product description for a soy candle.” You get a flat, generic paragraph about “warm, cozy vibes,” and you spend the next ten minutes rewording it.
The new way starts with a ramble. You mention that the shop is run by one person, that customers mostly buy gifts, that you hate words like “luxurious,” and that your last three descriptions all sounded the same. You add that the candles are poured in small batches and that the scents are named after places you’ve lived. The AI then writes a prompt that bakes in the gift angle, the banned words, the small-batch story and a request for variety across the product line. Same task, far better starting point.
Another commenter said that if more people worked like this, AI content would feel less robotic. That makes sense to me. Robotic output usually comes from thin input. Give the model your real situation and it has something real to work with.
How to Do It: Practical Steps
- 🧭 Explain the project. Say what it is and who it’s for, in plain words, as if talking to a friend. Mention the audience, the platform and the tone you’re after.
- 🎯 State the goal and the result you want. Be specific about what “done” looks like. A word count, a format, or a single sentence describing the reaction you want from the reader all help.
- ⚠️ Name your challenges. Tell it what keeps going wrong, what you’ve already tried, and what you don’t want. Past failures are some of the most useful context you can give.
- 📝 Keep talking until you’re out of things to say. Messy is fine. More context beats a neat summary. Voice dictation works well here, because speaking tends to surface details that typing hides.
- Ask for the prompt. Something like: “Using everything I’ve told you, write the single best prompt to achieve this. Ask me questions first if anything is unclear.”
- Run it. Paste the generated prompt into a fresh chat, or have the AI use it right there. A fresh chat keeps the output clean, while the same chat keeps all your context handy.
That last line in step 5 is a small tweak worth trying. Letting the AI ask you questions before it writes the prompt catches gaps you didn’t know you had. The original poster said they’re still refining the method and asked for suggestions, so this is one good place to start. Another is to save any generated prompt that works well and reuse it as a template. Over time you build a small library of prompts that already carry your voice, your rules and your preferences, and you only swap out the details for each new job.
One more tip: read the generated prompt before you run it. If it misses something important, tell the AI what to add instead of rewriting it yourself. Treat it like editing a draft from a teammate. A single round of feedback usually gets it where you want it.
Your Turn
Pick one task you’ve been fighting with this week. Skip the clever one-liner. Spend three minutes explaining the whole situation, then ask for the prompt. Compare the result to your last attempt. If it works for you, keep the habit and share your own tweaks with the community, because this one is clearly still evolving!
Something that’s been working for me
by u/CappetoteppaC in PromptEngineering