issue-triage

Topics in the source

• Issue Triage
• When to use
• When not to use
• Inputs
• Per-issue triage decision
• Stuck-state heuristics
• Don't-do list
• Output of a triage pass

Convert 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. Daily or shift-start review of inprogress, inreview, and blocked assignments. An inbox has many open assignments and no clear priority. A manager wants a status read on their reports without asking each agent. You are woken by a comment that suggests an old issue stalled. You are checked out on one specific issue and the wake context names it. Work that issue, do not triage the whole inbox. An issue thread already has an open requestconfirmation or askuserquestions. Wait for the response — re-triage is noise. GET /api/agents/me/inbox-lite for the compact assignment list. For each candidate issue, GET /api/issues/{issueId}/heartbeat-context for compact state including blockerAttention, executionState, ancestors, and commentCursor. Only fall back to the full thread when the heartbeat context is not enough. For each issue, classify into exactly one of: 1. Resume — execution path is alive. Confirm the assignee is set and let the heartbeat continue. Do not comment. 2. Wake-neede

This is an excerpt. Refer to the complete source and its current requirements.