From zsl
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
npx claudepluginhub zunosmartlabs/zsl-superpowersThis skill uses the workspace's default tool permissions.
Move issues on the project issue tracker through a small state machine of triage roles.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Move issues on the project issue tracker through a small state machine of triage roles.
Every comment or issue posted to the issue tracker during triage must start with this disclaimer:
> *This was generated by AI during triage.*
.out-of-scope/ knowledge base worksTwo category roles:
bug — something is brokenenhancement — new feature or improvementSix state roles:
needs-triage — maintainer needs to evaluateneeds-info — waiting on reporter for more informationready-for-agent — fully specified, ready for an AFK agentready-for-human — needs human implementationtracking — container/parent issue (e.g. a PRD) that has been broken into sub-issues; the real work lives in the childrenwontfix — will not be actionedEvery triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.
These are canonical role names — the actual label strings used in the issue tracker may differ. The mapping should have been provided to you - run /setup-zsl-superpowers if not.
State transitions: an unlabeled issue normally goes to needs-triage first; from there it moves to needs-info, ready-for-agent, ready-for-human, tracking, or wontfix. needs-info returns to needs-triage once the reporter replies. tracking is set automatically by /to-issues after it breaks an issue into sub-issues, and the parent auto-closes when the last child closes (no manual transition needed). The maintainer can override at any time — flag transitions that look unusual and ask before proceeding.
The maintainer invokes /triage and describes what they want in natural language. Interpret the request and act. Examples:
Query the issue tracker and present three buckets, oldest first:
needs-triage — evaluation in progress.needs-info with reporter activity since the last triage notes — needs re-evaluation.Show counts and a one-line summary per issue. Let the maintainer pick.
Gather context. Read the full issue (body, comments, labels, reporter, dates). Parse any prior triage notes so you don't re-ask resolved questions. Explore the codebase using the project's domain glossary, respecting ADRs in the area. Read .out-of-scope/*.md and surface any prior rejection that resembles this issue.
Recommend. Tell the maintainer your category and state recommendation with reasoning, plus a brief codebase summary relevant to the issue. Wait for direction.
Reproduce (bugs only). Before any grilling, attempt reproduction: read the reporter's steps, trace the relevant code, run tests or commands. Report what happened — successful repro with code path, failed repro, or insufficient detail (a strong needs-info signal). A confirmed repro makes a much stronger agent brief.
Grill (if needed). If the issue needs fleshing out, run a /grill-with-docs session.
Apply the outcome:
ready-for-agent — post an agent brief comment (AGENT-BRIEF.md).ready-for-human — same structure as an agent brief, but note why it can't be delegated (judgment calls, external access, design decisions, manual testing).needs-info — post triage notes (template below).tracking — the issue has open sub-issues; the work lives in the children. Apply the role and stop. Triage each child individually.wontfix (bug) — polite explanation, then close.wontfix (enhancement) — write to .out-of-scope/, link to it from a comment, then close (OUT-OF-SCOPE.md).needs-triage — apply the role. Optional comment if there's partial progress.Sync the project board (if configured). If docs/agents/project-board.md exists, after the label change above, also update the issue's project item Status:
docs/agents/project-board.md.gh api graphql -f query='query { repository(owner:"<owner>", name:"<repo>") { issue(number:N) { projectItems(first:20) { nodes { id project { id } } } } } }'
Filter by project.id matching the configured project node ID. If no match, log "issue not in configured project; skipping Status update" and continue.gh api graphql -f query='mutation($p:ID!,$i:ID!,$f:ID!,$o:String!){updateProjectV2ItemFieldValue(input:{projectId:$p,itemId:$i,fieldId:$f,value:{singleSelectOptionId:$o}}){projectV2Item{id}}}' \
-f p=<project-node-id> -f i=<item-id> -f f=<status-field-id> -f o=<option-id>
The label transition is the source of truth; the board sync is best-effort. If the Status update fails, surface the error but do not roll back the label change.
Skip this step entirely if docs/agents/project-board.md doesn't exist.
If the maintainer says "move #42 to ready-for-agent", trust them and apply the role directly. Confirm what you're about to do (role changes, comment, close), then act. Skip grilling. If moving to ready-for-agent without a grilling session, ask whether they want to write an agent brief.
## Triage Notes
**What we've established so far:**
- point 1
- point 2
**What we still need from you (@reporter):**
- question 1
- question 2
Capture everything resolved during grilling under "established so far" so the work isn't lost. Questions must be specific and actionable, not "please provide more info".
If prior triage notes exist on the issue, read them, check whether the reporter has answered any outstanding questions, and present an updated picture before continuing. Don't re-ask resolved questions.