triage

name	triage
description	Triage a Linear issue into type, priority, owner, team, labels, missing information, duplicates, and next step.

Triage

Use when a user asks for issue triage or whether an issue is actionable.

Process

1. Read the issue title, description, comments, labels, status, team, project, cycle, priority, and assignee. Done when every field is checked or noted as absent.
2. Search for related or duplicate issues using Linear MCP read tools. Done when at least one targeted search has run and top candidates are recorded.
3. Classify the issue type: bug, feature, task, incident, support, product question, cleanup, or unclear.
4. List missing information that blocks execution.
5. Propose priority, owner or owner team, labels, project or cycle, and next step. Every proposal must be evidence-backed from steps 1–2.
6. State recommendations separately from any actions already applied.

Output

Use the agent default response shape, plus classification and related or duplicate issues.