# Triage

> Move issues through a triage state machine. Use when reviewing bugs, feature requests, or preparing issues for implementation.

- Skill: `aquarius-mu/triage` (Agent Skill)
- Install (CLI): `npx skillmds@latest add aquarius-mu/triage`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aquarius-mu/triage/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML, Coding & Dev Tools
- Author: aquarius-mu (https://skillmd.com/u/aquarius-mu)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/aquarius-mu/triage

---


# Triage

Move issues through a state machine of triage roles.

Every comment posted during triage **must** start with:
```
> *This was generated by AI during triage.*
```

## Roles

**Category:**
- `bug` — something is broken
- `enhancement` — new feature or improvement

**State:**
- `needs-triage` — needs evaluation
- `needs-info` — waiting on reporter
- `ready-for-agent` — fully specified, AFK-ready (can be implemented without human input)
- `ready-for-human` — requires human judgment or external access
- `wontfix` — will not be actioned

Every triaged issue should carry one category and one state role.

## Invocation

Invoke `/triage` and describe what you want in natural language:
- "Show me what needs attention"
- "Triage issue #42"
- "Move #42 to ready-for-agent"

## Show What Needs Attention

Present three buckets (oldest first):
1. **Unlabeled** — never triaged
2. **`needs-triage`** — evaluation in progress
3. **`needs-info` with reporter activity** — needs re-evaluation

Show counts and a one-line summary per issue.

## Triage a Specific Issue

1. **Gather context.** Read the full issue. Explore the relevant codebase using domain vocabulary.

2. **Recommend.** State your category and state recommendation with reasoning. Wait for direction.

3. **Reproduce (bugs only).** Trace the relevant code path. Report whether the repro steps are coherent and what the likely code path is. A confirmed code-path trace makes a much stronger agent brief.

4. **Apply the outcome:**
   - `ready-for-agent` → post an agent brief (see template below)
   - `ready-for-human` → same structure, note why it can't be delegated
   - `needs-info` → post triage notes (see template below)
   - `wontfix` → polite explanation and close

## Agent Brief Template

```markdown
> *This was generated by AI during triage.*

## What to Build

[Concise description of the fix or feature, using domain vocabulary]

## Context

[Relevant code paths, module names, existing patterns to follow]

## Acceptance Criteria

- [ ] ./build.sh compiles clean
- [ ] Code review passed
- [ ] svn commit done with descriptive message

## C++ Conventions Reminder

- `SafeSub()` for subtraction
- `FindMapPtr` for map lookups
- `setChanged()` after data modifications
- `sendResponse()` only in CmdParser layer
- Full braces for all control flow
```

## Needs-Info Template

```markdown
> *This was generated by AI during triage.*

## Triage Notes

**What we've established:**
- [point 1]

**What we need from you (@reporter):**
- [specific question 1]
- [specific question 2]
```