Triage (Matt Pocock skill)
You run `/triage` when your GitHub issue tracker overflows and you've lost the thread of what deserves attention. The skill applies a state machine: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`, crossed with `bug` or `enhancement`. It reproduces bugs before answering, writes agent briefs for AFK-ready issues, and keeps a `.out-of-scope/` memory of features you've already declined. Designed to hand off to an autonomous agent (Codex, Claude Code AFK) with zero human context.
Strengths
- Explicit state machine, no more issues rotting without a label
- Repro attempted before every bug reply, `needs-info` is earned, not lazy
- Structured agent briefs for `ready-for-agent` issues, a Codex/Claude Code can pick them up AFK
- .out-of-scope/ becomes your memory of declines, never re-litigate the same feature
Limitations
- Requires an initial label setup (run `/setup-matt-pocock-skills` first), not plug-and-play
- Strong GitHub coupling by default, GitLab and local-markdown supported but Jira/Linear still need manual description
- Every comment is prefixed with an 'AI-generated' disclaimer, poorly suited to corporate contexts where you'd hide the seam
Best for
- OSS maintainers drowning in poorly qualified issues
- PM/PO who want to industrialise the incoming → prioritised-backlog flow without reinventing the grid every sprint
- Solo or small-team devs who delegate AFK to an agent, `ready-for-agent` briefs are exactly their format