Module 01 · Structural Prompt Frameworks
The RTF Framework for Fast, Everyday Prompts
Open lesson + course map
On this lesson
Course outline
Module 1 · Structural Prompt Frameworks
Module 2 · Reasoning Patterns
Module 3 · Few-Shot and Example-Driven Prompting
Module 4 · Reusable Instruction Systems
RTF stands for Role, Task, Format. It turns a vague request into a perspective, one action, and an answer shape.
Use RTF for low-stakes work like rewriting or extraction. You will build five prompts and learn when RTF is insufficient.
// concept
Build an RTF Prompt That Can Be Checked
The three fields do different jobs:
| Field | Write this | Quick test |
|---|---|---|
| Role | Relevant function or review lens | Does it change vocabulary, priorities, or checks? |
| Task | One verb, input, and hard constraints | Can you verify that the action happened? |
| Format | Output container and limits | Is the answer usable without reformatting? |
Bad prompt:
You are the world's best writer. Make this better.“World's best” adds no lens; “better” adds no test. A working version is:
Role: Act as a copy editor for concise business messages.
Task: Rewrite the message below for clarity. Preserve every date, price, and commitment; do not add facts.
Input: “Salam, confirming we can send the revised homepage on Thursday. The remaining PKR 18,000 is due after approval.”
Format: Return one message of 45–60 words, ready to paste into WhatsApp. Keep “Salam” and use plain English.The Task carries most meaning. Delete Role if it changes nothing. Format is a contract: “three bullets, each under 18 words” is testable; “make it nice” is not.
// concept
Pick Roles for Signal, Not Status
A useful role adds a professional lens; it does not guarantee correctness.
| Weak role | Better role | Signal added |
|---|---|---|
| “You are a genius marketing guru” | “Act as a Daraz catalog editor checking clarity and unsupported claims” | Claim control and buyer readability |
| “You are the world's greatest teacher” | “Act as a beginner programming tutor who demonstrates before defining” | Level and teaching sequence |
Mechanical extraction may need only Task and Format. Add “data-entry reviewer” when missing fields must be flagged rather than guessed.
// concept
Use RTF for Routine Work; Escalate by Risk
The examples below use sample data.
Role: Act as a customer-support editor for a Pakistani online shop.
Task: Rewrite the sample reply so it acknowledges the delay without promising a delivery date we do not have.
Input: “Your parcel is late. It should come soon.”
Format: Two sentences in natural Roman Urdu, under 45 words. End with one request for the order number.Sample output: “Parcel ki delay ka afsos hai. Order number share kar dein; hum status check karke confirmed update bhej denge.”
Role: Act as a project coordinator reviewing meeting notes.
Task: Extract only explicit actions from the sample notes. Do not infer owners or dates; write “not stated” when absent.
Input: “Hira will send the revised logo by Friday. The team discussed pricing. Bilal may review the copy.”
Format: Markdown table with columns Action, Owner, Due date, Confidence.Sample output: Send revised logo | Hira | Friday | explicit; pricing is omitted and Bilal's review is tentative.
Role: Act as a university writing tutor who protects academic honesty.
Task: Turn the sample thesis into three diagnostic questions the student must answer; do not rewrite the thesis or supply arguments.
Input: “AI is changing education in Pakistan.”
Format: Numbered list of exactly three questions covering scope, evidence, and counterargument.Sample output: “1. Which education level and AI use are you analysing?” It supports thinking without writing the assignment.
Choose RTF when input is present, there is one action, correction is cheap, and no sensitive decision depends on it. Escalate to CO-STAR when audience, tone, or context changes “good.” Add examples, sources, guardrails, and tests for high-stakes facts, dependent steps, or production reuse.
// worked_example
Worked Example
Bad prompt: Write a professional client update from these notes. It permits invented progress and accidental promises.
Sample input: “Homepage mobile fixes complete. Product-page copy waiting for client approval. Checkout test blocked because sandbox login has not arrived. Next: test once access arrives.” The freelancer runs:
Role: Act as a project coordinator writing factual updates for a UK client.
Task: Convert the notes below into a weekly update. Preserve the status of each item. Do not invent percentages, dates, causes, or commitments.
Input:
- Homepage mobile fixes complete.
- Product-page copy waiting for client approval.
- Checkout test blocked because sandbox login has not arrived.
- Next: test once access arrives.
Format: Use headings Completed, Waiting on you, Blocked, and Next. Maximum 90 words. Use calm British business English.Sample draft: “Blocked: Checkout testing is delayed due to missing sandbox credentials.” It is accurate, but “Waiting on you” assigns blame without naming an owner.
Fix Format: Use headings Completed, Awaiting input, Blocked, and Next; never assign responsibility unless the notes name an owner. Corrected sample: “Awaiting input: Product-page copy approval. Blocked: Sandbox login required before checkout testing can begin.” This preserves facts and tone.
// failure_cases
Failure Cases to Diagnose
6 cases to diagnose
Prestige-role theatre
“elite expert” adds no lens. Name the relevant function and concern.
Several tasks in one
“analyse, rewrite, and create a campaign” needs separate prompts or a prompt chain.
Missing source text
a summary request without the material invites assumptions. Attach and delimit the input.
Unmeasurable format
replace “brief and polished” with a container, length, and required fields.
Conflicting role
a “sales closer” pushes persuasion into a factual complaint reply; use a support lens.
RTF above its weight
medical, legal, financial, or production decisions need sources, tests, and qualified human review.
// pakistan_angle
Pakistan Angle
For Pakistani WhatsApp commerce, specify Urdu script, Roman Urdu, English, or a deliberate mix; preserve PKR amounts; and forbid invented delivery dates. Test Roman Urdu with the intended audience because spelling and formality vary.
Never paste CNIC numbers, bank details, phone numbers, private WhatsApp messages, or client credentials. Redact first and keep reusable prompts locally for load-shedding or weak-data periods. Saving RTF templates reduces retyping, not the need to check outputs.
// hands_on
Hands-On Exercise
Build five prompts for monthly tasks: rewrite a client message, extract actions, summarize a non-sensitive document, generate questions from your study notes, and format verified product information. For each, write Role, Task, Input, and Format; run one safe sample; and save an output excerpt. Remove roles that add no signal. Escalate one prompt to CO-STAR if audience, tone, or context changes its acceptance criteria. You are done when all five outputs can be checked objectively, without guessing what “good” means.
// completion_rubric
Completion Rubric
6 checks — tick as you verify
// sources
Sources
// check_yourself
Check yourself
4 questions · answers and options are taken word-for-word from this course
1 / 4 · diagnose
Your work shows this failure mode: “Prestige-role theatre.” The lesson describes it like this: ““elite expert” adds no lens.” What does the lesson tell you to do about it?