The 5-Part Prompt Template You Can Reuse for Almost Any Task

You have probably done this: typed a request, watched the answer arrive, and felt the small sag of disappointment. Technically it responded. Practically, you cannot use any of it. The request itself was not the problem. What went missing were the things a good colleague would ask before starting — who is this for, what does done look like, how should it sound, how long should it be.

Five slots close that gap. Role, task, context, format, example. Learn the shape once and you can point it at a blog post, a pile of survey comments, or a six-week launch plan without rethinking your approach every time.

Why Five Slots Beat One Long Instruction

A dense paragraph of instructions feels thorough. Usually it is not. When six requirements arrive in one breath, everything gets equal weight and the thing you care about most disappears into the middle.

Slots do two useful jobs. They force you to name what you want before you ask for it, and they separate the request from the packaging. A task says what to produce. A format says how to hand it over. Blur those two and you get an answer to a slightly different question than the one in your head.

Order matters too. Role and task go first. Context is wasted on a vague task, and a beautiful format cannot rescue a request nobody can pin down.

The Master Template

Copy this into a notes file and keep it near wherever you write. Filling it takes about ninety seconds.

Role: You are [specific job title plus one constraint].

Task: [One verb-first sentence describing exactly what to produce.]

Context: The audience is [who]. The situation is [what is going on]. Constraints: [length, tone, things to avoid, what has already been tried.]

Format: [Structure, order, length. Name the destination if there is one — email, slide, table, single paragraph.]

Example: [A sample of the style you want, or a bad sample with a note on why it fails.]

Anything you leave blank is a decision handed to someone else. Sometimes that is fine. When it is not, the blank shows up as output that feels almost right and is not.

How to Fill Each Slot Without Overthinking It

Role

Aim for a job title plus a bias. "You are a copy editor who cuts adjectives" beats "you are an expert writer." Specific, slightly opinionated roles push the output toward a point of view instead of a polite mush. One line is plenty.

Task

Start with a verb. Draft, rewrite, compare, rank, summarise, outline, critique. Keep it to one sentence. If you need three sentences to explain the job, you probably have two prompts — split them and run them in order.

Context

This is where most people underinvest. Write two to five lines covering who will read the output, what they already know, and what has already failed. Numbers, names and previous attempts are gold. If an earlier version felt too salesy, say so. That single line saves a revision later.

Format

Describe the shape, not the vibe. "Three bullet points under a one-line heading, under 80 words total" is usable. "Make it punchy" is not. If the output is headed somewhere specific, name the destination: a subject line, a table with three columns, a script meant to be read aloud.

Example

One sample does more work than a paragraph of description. Paste a paragraph whose tone you like. Or paste something you dislike and note the reason. If you have nothing at hand, ask for two versions in deliberately different styles, then keep the closer one — and use it as the example slot next time.

Three Filled-In Versions

For writing: a homepage paragraph

• Role: a direct-response copywriter who avoids hype and never uses exclamation marks.
• Task: rewrite the three product benefits below as a single homepage paragraph of 60 to 80 words.
• Context: readers are small business owners comparing two tools. They already know what the product does; they care about setup time. Avoid the word "solutions."
• Format: one paragraph, no heading, no bullets, plain sentences.
• Example: "Switching tools should take an afternoon, not a quarter. You import your list, you check the mapping, you go live." Match that rhythm.

For analysis: reading survey comments

• Role: an operations analyst who reads comments for patterns, not compliments.
• Task: group the 40 comments below into at most five themes and rank them by how often they appear.
• Context: these are post-purchase comments from people who cancelled within 60 days. I need to know what pushed them out, not what they liked. Comments are unedited.
• Format: a table with three columns — theme, rough count, one quote that captures it. Then two sentences on the theme that surprised you most.
• Example: a good theme label reads like "billing confusion after the trial ends." Specific, not "pricing."

If those findings will drive a real decision, check the counts against the source file before anyone acts on them.

For planning: a six-week launch

• Role: a project lead who plans in weeks and flags dependencies early.
• Task: draft a six-week plan for launching a paid newsletter to an existing email list.
• Context: one person doing the work, about eight hours a week. The list has 4,000 subscribers and has not been emailed in five months. No budget for paid ads. The first issue has to be finished before launch day.
• Format: a week-by-week list, each week with one goal and two or three tasks. Close with a short risks section, no more than four bullets.
• Example: "Week 2 — Goal: draft issue one. Tasks: outline, write the opening 500 words, book a test reader."

Mistakes That Flatten the Output

• A role that flatters instead of constrains. "World-class expert" tells nothing. "Editor who cuts 20% of every draft" tells everything.
• Format buried inside the task. Say what to write, then say how to hand it over.
• Context written as a mood. "Make it engaging" is not context. Audience and constraints are.
• Changing five things at once. When the output misses, adjust one slot and run it again. Otherwise you never learn which line did the work.
• Throwing away good output. When something lands, save it as the example slot. Your best prompts build themselves this way.

Make the Template a Habit

Start with the next thing you were going to write anyway. Fill the five slots in a scratch file, then paste it in. The first attempt will feel slow. The second takes a minute. By the fifth, you will be filling slots in your head before your fingers reach the keyboard.

Keep one rule: when the output misses, ask which slot was thin rather than whether the whole idea was bad. Nine times out of ten it is context or format. Fix that slot, run it again, and save the version that works. That saved block is worth more than any prompt you could copy from someone else's list, because it is calibrated to the way you actually work.

Photo: StartupStockPhotos / Pixabay