Prompts have a job
Make the release checklist testable
A quality bar turns “looks good” into pass, revise, or reject.
1Learn the idea
Read
Make each item observable
See it
Role + task + context + format = clearer output
“Check accessibility” is not testable. “Complete keyboard navigation of the purchase flow with no trap; record tester and result” is.
For each checklist item, request an action, expected result, evidence, and owner. The model may draft the structure, but it cannot honestly mark a test passed without test evidence.
Read
Guided practice
Rewrite “Make sure login works” as two testable checks: one normal case and one failure case.
Read
Independent transfer
Draft four acceptance checks for a small change. Ask a colleague to decide whether each can be answered yes or no from recorded evidence.
Read
Misconception
“Detailed output is evidence.” Detail can be invented. Evidence comes from an executed test, source record, or accountable observation.
Related lessons
Check your understanding
Page assessment
Answer from memory. Completion is saved from this evidence, not from opening the next page.
What must accompany a checked box before the release lead relies on it?
All responses are required.