Turn a vague bug report into a reproducible ticket

About this prompt

Translates an 'it's broken' message into a triage-ready ticket: steps to reproduce, expected vs actual, severity, and the first place to look in the code.

Prompt body

Rewrite this messy bug report as a triage-ready engineering ticket.

User's report:
"""
{{report}}
"""

Product / stack context:
"""
{{context}}
"""

Output:
- TITLE: one line, specific.
- STEPS TO REPRODUCE: numbered, minimal.
- EXPECTED vs ACTUAL.
- SEVERITY: blocker / high / medium / low, with one-line justification.
- LIKELY CAUSE: the first file or layer to investigate, and why.
- OPEN QUESTIONS: what to ask the reporter if repro is ambiguous.
Do not invent details the report doesn't support; list them as open questions instead.

Variables

Best for

• •First-use as-is; the defaults work.
• •Fork if your audience or voice is significantly different from the author's.
• •Chain into a workflow when one prompt isn't enough — multi-step flows are the usual next move.