Lab 5 · intermediate · About an hour

Turn a repeated task into a reusable prompt and context pack

Separate what stays the same from what changes, add real examples, and finish with a review checklist that someone else could apply.

You finish with

A packaged prompt with its context, examples and evaluation criteria, ready to hand to a colleague.

Before you start

  • A task you do at least weekly with an assistant.

Material: Your own working material. Anonymise anything sensitive before it goes in the pack.

  1. Do the task once and record everything

    Run it normally and save the prompt, the input and the output. This is your baseline.

    Checkpoint You have one complete example saved.

  2. Split stable from changing

    Two files. instructions.md holds everything true every time. input-template.md holds the shape of what changes. Most prompt libraries fail because these were written as one blob.

    Checkpoint Two files, no overlap.

  3. Write the evaluation criteria

    Three to five checkable statements about a good output. Checkable by someone who is not you.

    Checkpoint A colleague could apply them without asking a question.

  4. Add worked examples

    One or two complete input-and-output pairs. Include an awkward case, because that is what teaches the shape.

    Checkpoint At least one example is not the easy case.

  5. Test on three fresh inputs

    Typical, awkward, edge. Note failures against the criteria and fix the instructions, one change at a time.

    Checkpoint All three pass, or you know precisely why one does not.

  6. Hand it over

    Give the pack to someone else with no explanation. What they ask you is what the pack is missing.

    Checkpoint They produce an acceptable output without help.

The pack template
# instructions.md

Role: [only if it changes the output]
Task: [the verb, precisely]
Audience: [who reads the result]
Constraints: [length, register, banned words, must-include]
Output: [exact shape]

Evaluation — the output must:
1. [checkable]
2. [checkable]
3. [checkable]

If you cannot meet a criterion with the input given, say which and why rather than producing something that fails it.

# input-template.md

[Only what changes each time, with placeholders.]

# examples/

[One typical pair. One awkward pair.]

What finished looks like

A small folder — instructions, input template, two examples, criteria — that someone else can run cold. Expect the handover step to expose one thing you had been holding in your head.

Test criteria

  • Someone else runs it without asking you anything.
  • It handles the awkward input.
  • Changing the input file alone changes the output correctly.
  • The criteria can be applied by a third party.

If it goes wrong

Works for you, not for them.
You are supplying context implicitly. Whatever they asked you belongs in instructions.md.
Output drifts over time.
Version the pack and keep the test inputs beside it. Re-run them after any edit.

Privacy and safety

Anonymise the examples. A prompt pack gets shared more widely than the document it was built from.

Sources2 referenced
  1. Prompt engineering overview

    Anthropic · official guidance · link checked 2026-09-06

  2. Prompt engineering guide

    OpenAI · official guidance · link checked 2026-09-06

Links are checked at build time. If one has moved, tell us.

Read alongside

prompting

Iterate, evaluate and improve

The difference between someone good at this and someone frustrated by it is usually a habit of changing one thing at a time.