c_Learn & Practice AILEARN/Define what “done” means
← Level 2 · Better prompting
LEVEL 02 · 12 min

Define what “done” means

Acceptance criteria describe observable outcomes. “The form rejects an empty email and shows a readable error” is more useful than “make the form better”.

Before you begin

A brief Codex can act on

01

What is it?

Acceptance criteria describe observable outcomes. “The form rejects an empty email and shows a readable error” is more useful than “make the form better”.

02

Why it matters

Clear outcomes reduce avoidable misunderstandings.

03

When to use it

Before requesting a change with a concrete outcome.

04

How to do it

  1. Read the explanation and identify the files or environment involved.
  2. Write three checks for a contact form: valid submission, invalid input, and keyboard navigation. Specify the expected result for each.
  3. Compare the result with the verification criteria below. Record what worked and what remains unclear.
05

Worked example

Goal

Write three checks for a contact form: valid submission, invalid input, and keyboard navigation. Specify the expected result for each.

06

Try it yourself

Repeat the exercise with your own wording or a second sample. Use the smallest change that demonstrates the idea.

Prompt builder
07

Verify your result

A person who did not write the prompt can decide pass or fail for each check.

08

Common mistakes

Testing only the happy path. Include an invalid input and a recovery route.

09

How to recover

Stop at the first unexpected result. Preserve your current work, re-check the named file or environment, and repeat only the failing step. Ask for an explanation if the recovery is unclear.

Official references

Product interfaces and access can change. Use the linked official guide for current installation and account requirements.

OpenAI · Prompting ↗Source review: 2026-09-16
Checkpoint
Esc · Close