Level 200: Using gen AI well · Module 200.2

Three coworkers lean over a sheet as one points with a pencil.
Show what I can check

Prompts that hold up · Plain gear

What you will learn

Shown work may help but can contain errors or misstate how the answer was reached. Use a calculator for sums, open sources for quotes and citations, and check the conclusion.
Shown steps can help and still contain mistakes (s6); they may also misrepresent how the model arrived at the answer (s7). The verification checklist is course advice.
Figure data as text

Treat each step as a claim

PartWhat it means
WHAT IT TELLS YOU [s6, s7]Something to check, not proof. Shown steps can help, but can be wrong. They may not explain how it got the answer.
COURSE CHECKLISTUse an independent check. Redo sums with a calculator or spreadsheet. Open the source for quotes and citations. Check the final total or conclusion too.

In lesson 100.5 you learned to ask for one thing well. This lesson is about a prompt you will use a hundred times. Think of a recipe card in a busy kitchen. One good meal does not make a good recipe. A good recipe works on a busy night, with a new cook, when one ingredient has run out.

One rule from Level 100 stays the same. The AI writes a draft. A person checks it and decides.

A real case: writing down what the best people do

Some people think good prompting is a knack. You either have it or you don't, and you can't write it down. A real study is worth a look here.

Three researchers studied a large business-software company. Its support team answered customers' questions by online chat. The company gave the team an AI helper.1

That helper was a trained AI, not a written prompt. And it was one company.1 The study did not test a prompt at all. So here is what this course takes from it, as our own idea, not the study's finding. Some hard-to-explain skill could be learned from good examples. So it seems fair to think the easy-to-explain parts of a good request are worth writing down and sharing. Will your prompt help your team? You don't know yet. You find out by testing it, later in this lesson.

Notice one more thing. The helper stayed quiet when it did not know enough. A good prompt should tell the AI to do the same, and to pass the case to a person.

The six parts of a prompt you can reuse

A prompt template is like a form. Most of it stays the same. A few blanks get filled in each time, like this customer's email. This course uses six parts.

  1. The job. What to make, and who will check it. "Draft a reply. An agent will check it and decide whether to send it."
  2. The audience. Who will read it. "A customer who is not an engineer. Polite and short."
  3. The facts. Blanks for this case's facts, and the rule "use only these facts."
  4. An example. One good reply from before, made up or approved and with names removed.
  5. The format. Exactly how the answer should look, with a checklist at the end.
  6. When unsure. What to do if the facts don't answer the question. "Write NEEDS A PERSON and say what is missing."

Here is why the parts help.

At Big Widget Company (a made-up company), the warranty team's template asks for a reply and then a list called FOR THE AGENT. The list shows every date, amount and promise in the reply, and where each came from. The agent ticks each one against the claim record before sending, and reads the whole reply too.

Showing its working is not proof

Some jobs have several steps. Some people think that if the AI shows its working, the working is how it got the answer, and the answer must be right. Not so.

Steps can help. Researchers found that showing an AI a few worked examples, with every step written out, helped big AI models do better on maths, common-sense and symbol puzzles.6

Steps can be wrong. The same researchers say there is no guarantee the steps are right. They looked at 50 wrong answers. Some were almost right but had a simple sum done wrong.6 On most of their maths tests, using a real calculator for the sums helped.6

Steps may not be the real reason. Other researchers played a trick. In the examples they gave the AI, the right answer was always "A". The AI's answers were pulled off course, but its written explanations never mentioned the trick.7 Its working sounded sensible but did not tell the true story.7

So the working is like a list of claims. It is useful because you can check it. You still check it yourself.

What to do:

  1. Break the job into steps, and say what they are.
  2. Ask for working you can check without the AI: each number and where it came from, each quote word for word, each sum on its own line.
  3. Check each number in the source. Redo each sum on a calculator.
  4. Check the final answer too, not just the steps.
  5. If you can't check a number, say so. Mark it "not checked". Don't pass it on as a fact.

Don't ask the AI "are you sure?" as your check. A calculator and the source are your check.

A made-up example. Leila in finance asks an AI to estimate next year's warranty cost. She gives it three numbers: 1,240 widgets sold, 3.5 claims for every 100 widgets, and $820 for each repair. It shows its steps. Step 2 says there will be 434 claims. Leila checks on a calculator: it is about 43, not 434. The final total looked believable, but it was ten times too big. The neat steps did not make it right. Checking each step did. Leila, not the AI, decides what goes in the budget.

Working once is not working

Some people think that if a prompt worked once, it works. One good try on one easy case tells you very little. When someone says "it works", ask: out of how many tries?

A small test, the course's way:

  1. Write down what a good answer must do, and must never do.
  2. Collect six to ten examples. Include an easy one and some hard ones: a complaint, a question the facts can't answer, a long, messy email, and a request for something you must never promise.
  3. Use made-up examples, or real ones only if your workplace has approved them and names and details have been removed. Never test with live customer or company records. (Lessons 100.7 and 200.5 cover this.)
  4. Write down the right result for each one before you run it. Sometimes the right result is NEEDS A PERSON.
  5. Run each one and mark it pass or fail. Run the hard ones more than once. Write the score as a count, like "7 out of 8".
  6. Fix the prompt, then run them all again. Run them again whenever the prompt or the tool changes.

A prompt that has only been tried on thank-you notes has not been tested. Try the one that could make it fail. And if all of them pass, that means it has not failed yet on those examples. It does not mean it never will.

The three yeses, for a prompt

The Foundation uses three short phrases: Get to Yes, Stay at Yes and Recover to Yes.11 Its gate gives one of four answers: go ahead, only this far, wait for a person, or no.11

Keep the evidence, not the secrets. Keep your test examples and scores in your team's own files, if your workplace allows it. The Foundation's receipt is different. It never carries "prompts, outputs, payloads, personal data".5 So the test emails and replies stay in your work files, not in a receipt.

At Big Widget Company (a made-up story)

Sam runs a team that answers dealers' emails. Sam decides when a prompt is ready for the team. Each agent decides if a reply gets sent.

Remember

Words to know: prompt template (a prompt with blanks to fill in), example, working (the steps), edge case (an odd or hard example), test set (the examples you test with), gate (the point where a person says go ahead, only this far, wait, or no), not checked (the honest label for something nobody has checked yet).

Want to learn more? (optional)

These free university pages are extra reading. They are not where this lesson's facts come from.

Sources

  1. s9 Erik Brynjolfsson, Danielle Li, and Lindsey R. Raymond (2025). Generative AI at Work. Paper. Checked 2026-11-18 by source-checker (separate Claude Code session 1ac87f2f, round 2 re-check). ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩
  2. s1 Tom B. Brown et al. (2020). Language Models are Few-Shot Learners. Paper. Checked 2026-11-18 by source-checker (separate Claude Code session 9089430c). ↩ ↩
  3. s3 Anthropic (2026). Prompting best practices (Claude documentation). Official doc. Checked 2026-11-18 by source-checker (separate Claude Code session 1ac87f2f, round 2 re-check). ↩ ↩ ↩ ↩
  4. s5 Anthropic (2026). Reduce hallucinations (Claude documentation). Official doc. Checked 2026-11-18 by source-checker (separate Claude Code session 9089430c). ↩ ↩ ↩
  5. s11 AiGovOps Foundation (2026). AiGovOps Foundation Practice (home page). Official doc. Checked 2026-11-18 by source-checker (separate Claude Code session 1ac87f2f, round 2 re-check). ↩ ↩
  6. s6 Jason Wei et al. (2022). Chain-of-Thought Prompting Elicits Reasoning in Large Language Models. Paper. Checked 2026-11-18 by source-checker (separate Claude Code session 1ac87f2f, round 2 re-check). ↩ ↩ ↩ ↩
  7. s7 Miles Turpin, Julian Michael, Ethan Perez, and Samuel R. Bowman (2023). Language Models Don't Always Say What They Think: Unfaithful Explanations in Chain-of-Thought Prompting. Paper. Checked 2026-11-18 by source-checker (separate Claude Code session 1ac87f2f, round 2 re-check). ↩ ↩ ↩
  8. s8 Melanie Sclar, Yejin Choi, Yulia Tsvetkov, and Alane Suhr (2023). Quantifying Language Models' Sensitivity to Spurious Features in Prompt Design or: How I learned to start worrying about prompt formatting. Paper. Checked 2026-11-18 by source-checker (separate Claude Code session 9089430c). ↩ ↩
  9. s2 Anthropic (2026). Prompt engineering overview (Claude documentation). Official doc. Checked 2026-11-18 by source-checker (separate Claude Code session 9089430c). ↩ ↩
  10. s4 Anthropic (2026). Define success criteria and build evaluations (Claude documentation). Official doc. Checked 2026-11-18 by source-checker (separate Claude Code session 1ac87f2f, round 2 re-check). ↩ ↩
  11. s10 AiGovOps Foundation (2026). Manifesto. Official doc. Checked 2026-11-18 by source-checker (separate Claude Code session 1ac87f2f, round 2 re-check). ↩ ↩

Next: the quiz