Three sentences. That’s often the gap between a flat ChatGPT answer and one that reads like a senior consultant wrote it.
u/SpellZealousideal168 broke this down in a short post on r/ChatGPTPromptGenius, and it’s worth stealing. Most people type a question, hit enter, and hope for a sharp answer. The original poster’s fix skips the hoping part entirely, and it changes the output fast.
🎯 Quick start: every strong prompt needs three pieces stacked together. Role, task, format. Skip one and the model fills the gap with its own guess, which is exactly where generic answers come from.
Here’s why that matters more than it sounds. ChatGPT doesn’t actually know what you want. It knows what your words statistically suggest you want, and vague words suggest vague answers. Structure removes the guessing.
The Old Way vs The New Way
The old way looks like this: “Write about marketing.” ChatGPT has no idea who it’s supposed to sound like, what “about” means, or how long the answer should run. So it picks the safest, blandest option available. That’s not the model being lazy. That’s the model doing exactly what an underspecified prompt asked for.
The new way stacks three layers before the question even lands. First, a role: “Act as a senior growth marketer who’s launched 20 SaaS products.” Second, a clear task: “Write three cold email subject lines for a B2B onboarding tool.” Third, a constraint: “Keep each one under 8 words, no clickbait.” Same model, same day, a completely different output!
Put together, that’s one prompt instead of three separate instructions:
Act as a senior growth marketer who’s launched 20 SaaS products. Write three cold email subject lines for a B2B onboarding tool. Keep each one under 8 words, no clickbait.
The contrast isn’t subtle. The vague version produces a Wikipedia summary. The structured version produces something you could paste into a live campaign today.
The Three-Part Structure
Here’s the breakdown the original poster shared, in order. Each piece does a different job, and skipping one weakens the whole prompt.
- Role or context. Tell ChatGPT who it’s acting as. “Act as a senior Python developer” works better than “help me with code.” It loads in an entire frame of expertise before the task even starts.
- Clear task. Spell out exactly what you want done. Not “help with my email,” but “write a follow-up email to a client who missed a deadline.”
- Constraints and format. This is where most loose prompts fall apart. “Summarize in bullet points,” “avoid technical terms,” “keep it under 100 words.” Pick limits that match where the answer is actually going.
Stack all three in one message and you’ve done more real prompt engineering than most people manage in a week of daily ChatGPT use. One caveat worth naming: a quick factual question doesn’t need all three layers. Save the full structure for anything you’re going to publish, send, or ship.
Two Upgrades From the Comments 💬
The discussion under the post added two moves worth folding into this structure.
One commenter’s trick: feed the model a bad answer and ask what went wrong with it. That forces ChatGPT to diagnose its own failure mode instead of you spelling out every rule up front. It saves real time on long prompts. Something like:
Here’s an answer that didn’t work for me: [paste it]. What’s wrong with it, and what would you change?
Another commenter pushes it further with a triple-pass critique. Ask ChatGPT to critique its own answer, then ask why it missed those problems the first time. Then have it write a standard so it doesn’t repeat the mistake. It’s more steps. But for anything you plan to reuse, like a weekly template, the extra round trip pays for itself.
I tried the role-task-constraint stack on a rewrite I’d been putting off for weeks, and the first draft came back usable. That almost never happens on the first try, and it’s the clearest proof this structure isn’t just theory.
Try It on Your Next Prompt
Next time you open ChatGPT, don’t type the question first. Write the role, then the task, then the constraint, in that order. Three sentences, maybe four, and the output stops sounding like everyone else’s.
A few starting points worth testing this week:
- Swap your usual “write me X” prompt for the full three-layer version and compare the two outputs side by side.
- Save your best structured prompts somewhere you’ll actually find them again, not buried in old chat history.
- Try the bad-answer trick on a prompt you’ve already given up on.
Go check out the original thread in r/ChatGPTPromptGenius. The comments hold more real examples than this post could fit, and that’s exactly where the best prompt tricks tend to live.
Frequently Asked Questions
Q: How do I get ChatGPT to catch its own mistakes?
Instead of listing every rule upfront, give ChatGPT an example of a bad answer and ask what went wrong. This triggers self-correction without you spelling out every constraint. You can also ask it to critique its own response multiple times, then ask why it missed those problems, this helps it develop better thinking standards for the future.
Q: Should I ask ChatGPT to repeat back my requirements?
Yes, it helps. Have ChatGPT repeat back what you’re asking for before it answers. Then ask it to write the prompt structure it actually needs to succeed. This catches misunderstandings early and keeps the model locked on what matters.
Q: Is it better to give examples or write strict rules?
Both work differently. Writing strict rules feels tedious and often incomplete. Giving a bad example and asking what went wrong is usually faster, ChatGPT learns through negative feedback without you having to spell out every detail.
Q: How many times should I iterate before my prompt is ready?
It depends on the task, but the “triple pass” approach works well: ask for an answer, critique it, then ask how the model will solve those problems in the future. Have it write standards or a checklist to follow before answering. Keep iterating until the output matches what you need.
How to Structure ChatGPT Prompts to Get Much More Precise and Professional Answers
by u/SpellZealousideal168 in ChatGPTPromptGenius