Issue Triage Decision
By Kenji · Published · Updated
Moves one issue through triage: reproduce it, classify it, size it and decide now, next or never, with the reason written down.
Prompt template
## Issue Triage Decision Triage this issue and record the decision. - Issue text: [textarea: Paste the report] - Reproduction details: [textarea: Steps or environment if known] - Product area: [text: Where it lives] - Open work for comparison: [textarea: Current priorities or milestone] - Capacity: [dropdown: Tight, Normal, Spare] 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.