Prompt Engineering for Content & SalesThe anatomy of a great prompt · Lesson 1 of 15

The six-part prompt: role, context, task, constraints, examples, format

Video lesson · 12 min · 9 min lecture

Video lecture

The six-part prompt: role, context, task, constraints, examples, format

11 chapters · about 9 min · full transcript

Coming soon

Chapter 1 of 11

The six-part prompt

  • Prompts are briefs
  • Six parts, one checklist

The narrated lecture is in production

Every chapter is scripted and ready. Browse the chapters and read the full transcript now — the video will appear here when it’s published.

Chapters

Prompts are briefs

The biggest shift in prompting is to stop thinking of a prompt as a question and start thinking of it as a creative brief. If you handed a freelancer the sentence "write a caption for my bakery", you would get something generic. If you gave them your audience, your offer, your tone and the platform, you would get something usable. AI works the same way.

A reliable structure has six parts. You will not always need all six, but checking against them fixes most weak prompts.

1. Role

Tell the model what expertise to bring. "You are a senior direct-response copywriter who specializes in Instagram ads for food brands in the Gulf." A role nudges vocabulary, priorities and standards. Keep it relevant; "world's greatest genius" adds nothing.

2. Context

This is where most prompts fail. Include:

  • Who you are: brand, product, price point, positioning.
  • Audience: who they are, what they want, what they worry about, what language they use.
  • Situation: campaign goal, platform, season, what has worked before.
  • Facts the model must use: approved claims, prices, dates.

3. Task

One clear verb and deliverable: "Write five caption options", "Rewrite this email", "Summarize these reviews into three themes". If you have several tasks, number them or split them into separate prompts.

4. Constraints

The rules: length, tone, words to avoid, compliance requirements, reading level, language variety (British or American English, Gulf or Levantine Arabic, Urdu or Roman Urdu).

Examples: "Under 150 characters before the 'more' cut-off." "No health claims." "Do not use the words 'elevate', 'unlock' or 'game-changer'." "Include #ad at the start because this is a paid partnership."

5. Examples

Show, don't just tell. One or two examples of captions you love, or past posts that performed well, teach tone faster than any adjective. (More on this in the next lesson.)

6. Output format

Say exactly how you want the answer: a numbered list, a table with columns, a script with timestamps, JSON for a spreadsheet, or "hook on line one, body, then CTA".

Before and after

Weak: "Write a caption for my bakery's new cake."

Strong:

Role: You are a social media copywriter for independent food brands in Pakistan. Context: We are Crumb & Co, a home bakery in Lahore selling custom cakes (from PKR 4,500). Audience: women aged 25–40 planning birthdays, who order via WhatsApp. Our tone is warm, playful and slightly cheeky. We are launching a pistachio-rose cake for Eid. Task: Write five Instagram caption options for the launch Reel. Constraints: Each under 60 words. First line must work as a hook on its own. Mix English with light Roman Urdu. No claims about being "the best in Lahore". End with a CTA to WhatsApp. Example of our voice: "Birthday on Saturday and zero plan? Relax, jaan. We've got the cake. You bring the candles." Format: Numbered list, each option followed by a one-line note on the angle used.

The second prompt takes two extra minutes to write and saves twenty minutes of editing.

Where the six parts live in 2026 assistants

You don't have to type all six parts every time. Modern assistants let you store the stable parts once:

PartStable or per-task?Where to store it
RoleMostly stableProject instructions, a custom GPT, a Gemini Gem, Claude project instructions
ContextBrand context stable; campaign context per taskProject files (voice guide, product sheet) + a few lines per task
TaskPer taskThe prompt
ConstraintsBrand rules stable; task limits per taskProject instructions + the prompt
ExamplesMostly stableProject files ("best posts", "best emails")
FormatPer task, or saved defaultsThe prompt, or project instructions for defaults

With a well-built project, your everyday prompt shrinks to task, task-specific context and format, and the output still reflects all six parts.

Hands-on: rebuild one of your own prompts

Take the last prompt you used for content or sales. Paste it into this checker:

Here is a prompt I used: [paste].
Check it against six parts: role, context, task, constraints, examples, output format.
For each part: present / missing / weak, and one specific improvement.
Then rewrite the prompt with the improvements, using [PLACEHOLDERS] for facts only I can supply.
Do not invent facts about my business.

Before: "Write a LinkedIn post about our new HR software feature."

After: a structured prompt with a role (B2B SaaS content writer for HR leaders), context (the feature, the audience's pain in their words, one approved customer result as [PROOF]), a single task, constraints (under 180 words, first line under 12 words, no "revolutionary"), one example post, and a format (hook, 3 short paragraphs, question to prompt comments). Fill the placeholders and you'll typically go from four rounds of editing to one.

Quick checklist

Before you hit enter, ask:

  • Would a human freelancer understand exactly what I want?
  • Did I give facts the model cannot guess?
  • Did I say what to avoid?
  • Did I specify the format I need?

Pitfalls

  • Over-stuffing: a two-page prompt full of irrelevant history can dilute the key instructions. Put the most important rules near the task, and keep context relevant.
  • Conflicting instructions: "Be concise" and "include every detail" pull in opposite directions. Decide which wins.
  • Relying on role alone: "You are an expert marketer" without context still produces generic work.

Key takeaways

  • Treat prompts as creative briefs: role, context, task, constraints, examples and output format.
  • Context is the part most often missing; supply facts the model can't guess.
  • Store stable parts (role, brand context, rules, examples) in a project, GPT or Gem; type only the task-specific parts.
  • Avoid over-stuffing and conflicting instructions; put the most important rules near the task.

Check your understanding

Quick questions to lock in the lesson. They don’t count towards your certificate.

  1. Which part of a prompt is most often missing when output feels generic?
  2. 'Do not use the words elevate or unlock' is an example of which prompt part?
  3. What is the main risk of a very long prompt packed with background?

Put it into practice

Rewrite one of your recent weak prompts using all six parts, run both versions, and compare how much editing each output needs.

Enrol for free to save your progress

Reading is always free. Enrol to keep your place, take the final assessment and earn a verifiable certificate.