Turn a bug into a reproducible report
A reproducible report records what you expected, what happened, the exact steps, and the environment. Redact secrets from error messages before sharing.
What is it?
A reproducible report records what you expected, what happened, the exact steps, and the environment. Redact secrets from error messages before sharing.
Why it matters
A reproduced failure is easier to diagnose than a guess.
When to use it
When actual behavior differs from the expected result.
How to do it
- Read the explanation and identify the files or environment involved.
- Describe a broken navigation link: open the page, select the link, record the destination and error. Include the expected destination and permitted files.
- Compare the result with the verification criteria below. Record what worked and what remains unclear.
Worked example
Describe a broken navigation link: open the page, select the link, record the destination and error. Include the expected destination and permitted files.
Try it yourself
Repeat the exercise with your own wording or a second sample. Use the smallest change that demonstrates the idea.
Prompt builderVerify your result
A second person can reproduce the same failure using your steps.
Common mistakes
Sending only “it is broken”. Add the failing action and observed evidence.
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 · Quickstart ↗Source review: 2026-09-16