Turn a vague bug report into concrete reproduction steps
Takes an unstructured user report and produces a numbered sequence an engineer can follow, with anything the report does not specify marked.
Read the bug report below and produce numbered reproduction steps.
Each step should be one concrete action. Include starting state, exact inputs where given, and expected versus actual result at the end.
Where the report does not specify something needed to reproduce it - browser, account state, exact input - write "not specified: <what is missing>" instead of guessing a plausible value.
--- report ---
{{report}}Fill these in
Type your values and Copy gives you the finished prompt, not the template.
Nothing filled in yet - Copy will give you the template with placeholders.
Notes from the author
The not specified rule is what makes the output safe to give to someone who was not there. Without it the model fills the gaps with the most common case, and an engineer spends an hour reproducing the wrong scenario.
For information only, not professional advice. You use it at your own risk and we are not liable for any loss or damage. See the disclaimer.
Tagged