---
name: issue-triage-decision
description: "Moves one issue through triage: reproduce it, classify it, size it and decide now, next or never, with the reason written down. Use when a new bug report or request needs a classified, sized and prioritised decision with the reasoning recorded. Do not use for fixing the bug or planning a whole release. Related topics: product, coding."
---

# Issue Triage Decision

Moves one issue through triage: reproduce it, classify it, size it and decide now, next or never, with the reason written down.

## When to use

Use this skill when a new bug report or request needs a classified, sized and prioritised decision with the reasoning recorded. Do not use it for fixing the bug or planning a whole release.

## 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. Check the report for reproduction details and list or request anything missing.
3. Attempt reproduction and classify the issue as bug, regression, request, question or duplicate.
4. Assess impact by who is affected, how often and whether a workaround exists, then size the effort.
5. Decide now, next, later or never against open work and capacity, with a two-sentence reason.
6. Produce the labels to apply and the comment to post, including a kind closing note for a never.

## Inputs

- **Issue text** (longer free text)
- **Reproduction details** (longer free text)
- **Product area** (free text, e.g. "Where it lives")
- **Open work for comparison** (longer free text)
- **Capacity** (choose one: Tight, Normal, Spare)

## Output

A triage record with classification, impact, size, decision, the two-sentence reason, labels and a ready-to-post comment.

## Prompt template

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

### Issue Triage Decision

Triage this issue and record the decision.

- Issue text: {{Issue text}}
- Reproduction details: {{Reproduction details}}
- Product area: {{Product area}}
- Open work for comparison: {{Open work for comparison}}
- Capacity: {{Capacity}}

First check the report is complete; list anything missing that stops reproduction and ask for it, or label it needs-info. Try to reproduce it from the report and say the result. Classify it: bug, regression, feature request, question or duplicate, and name the duplicate if there is one. Judge impact by who is affected, how often and whether there is a workaround. Size the effort as small, medium or large with the main reason. Then decide: now, next, later or never. Compare against the open work and the capacity, and justify the call in two sentences someone can disagree with. If it is never, write a kind closing note that explains why. End with the labels to apply and the comment to post.

## Pitfalls

- Deciding by who shouted loudest rather than by impact and frequency.
- Closing as never with no explanation, which discourages future reports.
- Skipping reproduction, so the issue is sized on a guess.