batch-triagelisted
Install: claude install-skill thientranhung/astragentic
# Batch-triage an inherited backlog
The plugin's `triage` handles one item arriving now. An inherited backlog is a different
shape: a hundred items of unknown age, written by people who are not here, about code that
has moved since. This skill is the one-pass version, and its output feeds Thomas's frontier.
**Extract, never invent.** Every classification cites the item's own text or the code it
names. An item you cannot classify from evidence is classified `NEEDS-OWNER`, which is a real
outcome and takes one line.
## 1. Read the vocabulary first
Load `docs/agents/triage-labels.md` — the label set is the project's, produced by
`setup-matt-pocock-skills`, and inventing a parallel vocabulary here would fork it.
**Then read the tree, not a map of it.** Most triage decisions turn on whether the code an
item names still exists, so resolve each item against the CURRENT tree with `rg` and `git
log`. A map would be faster and would also be the thing most likely to be stale exactly
where triage needs it: on code that moved
or died.
## 2. Classify each item against the code
For each item, answer three questions in order. The first that resolves it wins, so most
items cost very little.
1. **Does the thing it describes still exist?** Grep for the files, symbols and routes it
names. Nothing left → `STALE`, citing what you searched for and did not find. This is the
largest category in most inherited backlogs and the cheapest to establish.
2. **Has it already been done?** Check