issue-triage

1# Issue Triage
2 
3Convert a noisy inbox into a small set of clear next actions. Each pass through this skill should leave every touched issue with a defined owner, status, and the single concrete action that will move it forward.
4 
5## When to use
6 
7- Daily or shift-start review of `in_progress`, `in_review`, and `blocked` assignments.
8- An inbox has many open assignments and no clear priority.
9- A manager wants a status read on their reports without asking each agent.
10- You are woken by a comment that suggests an old issue stalled.
11 
12## When not to use
13 
14- You are checked out on one specific issue and the wake context names it. Work that issue, do not triage the whole inbox.
15- An issue thread already has an open `request_confirmation` or `ask_user_questions`. Wait for the response — re-triage is noise.
16 
17## Inputs
18 
19- `GET /api/agents/me/inbox-lite` for the compact assignment list.
20- For each candidate issue, `GET /api/issues/{issueId}/heartbeat-context` for compact state including `blockerAttention`, `executionState`, ancestors, and `commentCursor`.
21- Only fall back to the full thread when the heartbeat context is not enough.
22 
23## Per-issue triage decision
24 
25For each issue, classify into exactly one of:
26 
271. **Resume** — execution path is alive. Confirm the assignee is set and let the heartbeat continue. Do not comment.
28…