issue-triagelisted
Install: claude install-skill StGerman/crewd
# Issue triage
The backlog is this repository's GitHub Issues. The daemon reads it directly: an open issue
that is labelled `agent` **and** has an assignee is work a real agent will pick up and spend
tokens on. The label is `tracker.required_labels`; the assignee is `GithubTracker`'s
`dispatchable` rule (`to_issue` in `src/tracker/github.rs`). Both must hold, so re-read that
function if the rule may have moved. Triage
is therefore the decision point between "someone wrote this down" and "an agent works this" —
treat it as the gate it is.
## States
Every open issue is in exactly one state. Check the rows top-down; the first match is its
state.
| State | On GitHub | Meaning |
|---|---|---|
| **Inbox** | no milestone | Nobody has looked at it yet. The default for every new issue. |
| **Backlog** | milestone **"Worth doing, not scheduled"** | Triaged and accepted, with no date. |
| **Dispatchable** | current milestone, labelled `agent`, **and** at least one assignee | The daemon will pick it up. |
| **Planned** | any other `M<n>` milestone | Committed. The milestone *is* the priority. |
A current-milestone issue missing either `agent` or an assignee is **Planned**, not
Dispatchable: report it that way, because the daemon will never run it. An issue triage decides
against leaves the set: it is closed as *not planned* with a one-line reason.
Keeping Backlog as a real milestone is what makes "no milestone" mean *untriaged* and nothing
else, so `is:open no:milestone` is the com