triage — Issue Triage

• Trigger: /triage or keywords "triage", "classify", "prioritize"
• Best for: Managing issue queues, assessing bug priority, organizing feature requests
• Not for: Fixing bugs, detailed requirement analysis

Overview

triage uses a state-machine-driven triage process to quickly assess and classify issues/bugs/requests. It evaluates each entry through predefined triage roles: validity → priority → assignment.

Trigger Conditions

triage auto-triggers when you:

• Mention batch processing issues
• Need to assess and classify requests/bugs
• Use the /triage command

Examples

Example 1: Batch Issue Triage

/triage Help me triage the 15 new GitHub issues from the past week

Claude evaluates each issue on:

1. Validity: Reproducible? Sufficient info?
2. Priority: P0 (urgent) to P4 (long-term)
3. Category: Bug / Feature / Enhancement / Question
4. Assignment: Suggested owner

Example 2: Single Bug Triage

/triage User reports the payment page is blank on Safari, no version info provided

Claude will:

• Flag as "Needs Info", generate follow-up questions
• Suggest provisional high priority (payment-related)

Example 3: Feature Request Backlog

/triage Here are 20 feature requests from the product team — categorize and prioritize

Example 4: Incident Triage

/triage A security vulnerability was just found in production — assess severity and response level

Example 5: Tech Debt Triage

/triage Code scan found 50 warnings — categorize which need immediate attention

Triage Dimensions

Dimension	Options	Description
Type	Bug / Feature / Enhancement / Tech Debt / Question	Nature of the issue
Priority	P0 - P4	Urgency level
Impact	Critical / High / Medium / Low	User impact
Reproducibility	Always / Sometimes / Once / Unknown	Bug stability
Status	Needs Info / Ready / In Progress / Blocked	Current state

Notes

• Triage is assessment, not resolution — use other Skills for action
• Flag insufficient-info items as "Needs Info" rather than closing
• Priority = user impact × probability × fix cost
• For batch triage, keep batches under 20 items for quality

Related Skills

• to-issues — After triage, break confirmed items into dev tasks
• diagnose — After confirming a bug, start diagnosis
• to-prd — Large features after triage → PRD