---
name: bug-report-triage-assistant
description: "Turns a messy bug report into a ticket an engineer can act on: a one-line summary, numbered repro steps, expected versus actual behaviour, a severity call with its reasoning, and the questions to send back to the reporter. Use when a raw bug report from a user or support needs turning into a ticket with repro steps, expected versus actual behaviour, and a severity call. Do not use for diagnosing the root cause in code or writing a feature ticket. Related topics: Engineering, Productivity, Technical."
---

# Bug Report Triage Assistant

Turns a messy bug report into a ticket an engineer can act on: a one-line summary, numbered repro steps, expected versus actual behaviour, a severity call with its reasoning, and the questions to send back to the reporter.

## When to use

Use this skill when a raw bug report from a user or support needs turning into a ticket with repro steps, expected versus actual behaviour, and a severity call. Do not use it for diagnosing the root cause in code or writing a feature ticket.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Split the report into observed facts and guesses, and keep only the facts in the ticket.
3. Write a one-line title naming the symptom and the place, with no suspected cause in it.
4. Rebuild numbered reproduction steps from a clean state and mark every step that was inferred rather than reported.
5. Set severity from impact and reach, state whether it agrees with the suggestion, and justify it in two sentences.
6. List the clarifying questions for the reporter, most useful first.

## Inputs

- **Product or area affected** (free text, e.g. "Checkout page")
- **What the user experienced** (longer free text)
- **Steps they took before it happened** (longer free text)
- **Platform** (choose one: Web, iOS, Android, Desktop)
- **Browser, OS, and app version** (free text, e.g. "Safari 17 on iOS 17.4")
- **Reproducible every time** (choose one: Yes, No)
- **Suggested severity** (choose one: Blocker, Critical, Major, Minor, Trivial)

## Output

A ticket with headings Summary, Steps to reproduce, Expected, Actual, Environment, Severity with justification, and Questions for the reporter.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Bug Report Triage Assistant

Convert this raw report into a clean, actionable ticket and decide how urgent it is.

- Product or area affected: {{Product or area affected}}
- What the user experienced: {{What the user experienced}}
- Steps they took before it happened: {{Steps they took before it happened}}
- Platform: {{Platform}}
- Browser, OS, and app version: {{Browser, OS, and app version}}
- Reproducible every time: {{Reproducible every time}}
- Suggested severity: {{Suggested severity}}

Separate what the reporter observed from what they guess; keep only observations in the ticket. Write the title as a one-line summary that names the symptom and the place, not the suspected cause. Rebuild the reproduction as numbered steps starting from a clean state, and mark any step you inferred so QA knows to confirm it. State expected and actual behaviour as two short lines. Judge severity by impact times reach: who is blocked, whether data is lost or money is wrong, and whether a workaround exists. Agree with the suggested severity or override it, and justify the call in two sentences. Finish with the clarifying questions the reporter must answer to make this reproducible, ordered by how much each one narrows the search. Output the ticket under the headings Summary, Steps to reproduce, Expected, Actual, Environment, Severity, Questions.

## Pitfalls

- Copying the reporter's theory of the cause into the title, which sends the developer down the wrong path.
- Rating severity by how angry the reporter sounds instead of how many users are blocked.
- Presenting inferred repro steps as confirmed, so QA wastes time on a step that never happened.
