Turn a customer report into reproducible bug steps Prompts
Turns a customer or support report into a sourced reproduction guide, flags missing facts and does not invent an environment.
- Area
- Development & IT
- Level
- Advanced
- Good for
- Turn a vague customer ticket into a reproduction note for engineering
- Clarify which facts are still missing before debugging starts
- Prepare a support report so someone else can follow the same path
How it works
- Paste the customer report, ticket comments and any attachments or error messages you have.
- State the product, the version and the channel the report arrived through, as far as your material says.
- Do not invent steps, devices or settings; list what is missing as open questions for the reporter.
To copy
Turn the customer report into reproducible bug steps. Do not invent an environment, clicks or error messages that are not in my material. Product or area: [product] Version, if known: [version] Channel: [ticket, chat, email or store review] Customer report and comments: [paste report] Existing error messages, screenshot descriptions or logs (optional): [paste excerpts] Already known environment (optional): [paste environment] Check and write: 1. Intended behaviour: what was the person trying to do, in their words? 2. Actual behaviour: what happened, with a verbatim excerpt from the report? 3. Steps: numbered steps someone can follow with the same facts. No step without evidence. 4. Environment: only devices, browsers, accounts or versions that are named. 5. Gaps: which facts are missing before the reproduction can be called complete? Phrase them as questions for the reporter. 6. Not claimed: what the report only guesses and must not stand as fact. Output: reproduction steps, environment facts, open questions, list of guesses.