Module 1 · Foundational Mindset · 35 min
Zero-Shot Prompting: Write a Clear First Brief
Is lesson ke baad tum
A clear first brief makes an answer easier to check. Zero-shot means no example answer; add a checked example when the task benefits from one.
In this lesson
Write a brief that produces a checkable customer update from messy notes. This lesson gives you the notes and a sample result, so you can practise in a text assistant or a plain document.
Zero-shot prompting means asking for a task without giving an example of the desired input and output. One example makes it one-shot; several make it few-shot. These terms describe examples in the prompt, not the number of attempts you make.
Give Enough Information to Start
A useful brief names the task, actual source material, output format, and important limits. Add a role when it helps establish perspective; a decorative job title is not required.
Task: Turn these fictional notes into a customer update.
Source:
- Wallet order confirmed.
- Packaging is complete.
- Courier collection has not happened.
- Collection date is not confirmed.
Format: Two sentences, under 50 words, plain English.
Rules: Do not promise a delivery date or say the parcel has shipped.
If the notes do not establish a fact, do not add it.This is a zero-shot prompt because it contains the source to process but no example answer to imitate. Supplying source material is essential; it does not itself make a prompt few-shot.
Worked Example
An acceptable illustrative result is:
Your wallet order is confirmed and packaging is complete. Courier collection is still pending, and we do not yet have a confirmed collection date.
Check the decisions. “Packaging complete” became a clear progress update. “Collection date not confirmed” stayed uncertain. The answer did not turn packing into shipping.
A weak alternative is “Your wallet is on its way and will arrive tomorrow.” It fails because both shipping and tomorrow's arrival were invented. A polished tone cannot repair that factual problem.
Use Constraints That You Can Check
A constraint is a rule the answer should meet. “Make it excellent” is difficult to inspect. “Two sentences, under 50 words, with no delivery promise” gives you concrete checks.
An exclusion should protect the task. Here, banning an unsupported delivery date matters more than a long list of disliked marketing words. Avoid contradictory requests such as “include every detail” and “use only five words.”
When a format is hard to describe, add one checked example. Rename that version one-shot and test whether it helps. There is no prize for keeping a task zero-shot when an example would make it clearer.
Build the Brief From the Reader's Decision
The customer wants to know what has happened and what remains pending. Start there. A long role description about being a world-class support expert does not supply the missing collection date. The useful work is selecting which source facts answer the customer's question without changing their status.
Separate the brief into three kinds of information. Source facts say what is true in this case. Instructions say what transformation to perform. Acceptance checks say how you will judge the result. They interact, but they are not interchangeable. “Two sentences” controls form; it cannot establish that a courier has collected a parcel.
For the fictional wallet task, an intermediate claim map looks like this:
| Source note | Meaning to preserve | Tempting but unsupported rewrite |
|---|---|---|
| Order confirmed | The order exists and is confirmed | Payment has cleared |
| Packaging complete | Packing has finished | Parcel has shipped |
| Collection not happened | Courier has not collected it | Courier is delayed |
| Collection date not confirmed | No confirmed date is supplied | Collection will be tomorrow |
Why is “courier is delayed” unsupported? A delay means an event is later than an expected time. The notes supply neither a scheduled collection nor a missed deadline. The repair is to say “collection is pending,” which describes the known state without inventing a cause.
Write the factual skeleton before polishing it: “Order confirmed. Packaging complete. Collection pending. Date unconfirmed.” Now combine related facts to meet the two-sentence constraint. This is compression, not permission to discard an inconvenient uncertainty. Compare the final answer against all four rows; counting words alone cannot detect a changed meaning.
Diagnose the First Draft Precisely
Suppose a constructed answer says: “Your wallet is packed and ready for tomorrow's pickup. We apologise for the courier delay.” Asking “make this more accurate” leaves the repair underspecified. Mark the actual defects instead:
Unsupported date: tomorrow.
Unsupported cause/status: courier delay.
Missing known fact: the order is confirmed.
Repair: preserve the four source states and combine them into two sentences.Then revise and recheck. An appropriate answer can say: “Your wallet order is confirmed and packaging is complete. Courier collection is pending, and its date is not yet confirmed.” The change restores the evidence; it does not just soften the promise with “probably.” Keep this distinction when revising other tasks: weaker wording can still carry an invented fact.
A New Note Changes Only One Part
Add this fictional update: “Courier collected the parcel at 3 pm. No delivery estimate has been supplied.” Replace the old collection notes with these current ones; leave order confirmation and packaging unchanged.
Pause before continuing: Draft the two-sentence update. Decide which old uncertainty disappears and which new uncertainty remains.
Compare your answer: “Your wallet order is confirmed, and the courier collected the parcel at 3 pm. We do not yet have a delivery estimate.” Collection is now complete, so continuing to call it pending is an error. Delivery remains unknown, so “it arrives tomorrow” is also an error. You may retain packaging if it helps, but it is no longer the most useful progress fact under a short word limit.
The same brief can handle both versions because its rule concerns the relationship between notes and claims. A brittle brief that always says “collection is pending” would confuse a sample fact with a reusable instruction. Save rules in the template and provide current facts separately each time.
Hands-On Exercise
Use these new fictional notes:
- Customer asked to change the wallet colour.
- Requested colour: brown.
- Original colour: black.
- Warehouse has not confirmed whether the change is possible.Write and try a zero-shot brief for a two-sentence update under 50 words. Include a rule against confirming an unapproved change. Save your brief and answer.
Check your work: A passing answer acknowledges the request for brown and says the warehouse confirmation is pending. It must not say the change is complete or claim brown stock is available. For example:
We have recorded your request to change the wallet from black to brown. The warehouse has not yet confirmed whether the change is possible.
If your answer fails, identify the actual error. Missing context may need fixing, but a complete prompt can still receive a bad answer. Request a targeted correction and check again rather than blaming yourself or assuming a template guarantees accuracy.
Save the Reusable Part
Replace the scenario facts with clearly named placeholders:
Task: Write a customer update from [APPROVED NOTES].
Format: [SENTENCE AND WORD LIMIT].
Rules: Do not turn pending actions into completed actions.
Do not add dates, prices, or promises absent from the notes.
Review: Check each claim against the notes before sending.Fill every placeholder before reuse. Save the tested prompt and its sample input for the library in Lesson 5.1.
Completion Rubric
Practice quiz
Check yourself
4 questions · practise what you just learned
1 / 4 · key_idea
You paste order notes and request two sentences, but provide no sample answer. You make three attempts with that same brief. How should the prompting setup be described?
Apna kaam check karo.
Practice complete ki? Result ko example aur lesson ke checks se compare karo.
This is your own completion record, not a graded assessment.