Issue Triage

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.

When to use

• Daily or shift-start review of in_progress, in_review, 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.

When not to use

• 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 request_confirmation or ask_user_questions. Wait for the response, re-triage is noise.

Inputs

• 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.

Per-issue triage decision

For each issue, classify into exactly one of: