Repository navigation
Triage
Arnel Robles edited this page Oct 3, 2026
·
1 revision
Section 1 of the method. Sort the backlog yourself into three tiers and do tier 0 by hand.
Read the open issues once, yourself. Sort each into a tier and do the cheap ones by hand.
| Tier | What |
|---|---|
| 0 | docs, tests only, config, CI files, README sweeps |
| 1 | a feature inside one module, additive |
| 2 | core, auth, tenancy, data shape, anything reachable without a login |
Close duplicates and anything already solved by other means while you are in there. Do not file follow-ups. A review finding is fixed in the change or dropped. When one is real and cannot be fixed in the change, it goes on the checklist of the open issue that already owns that area, as section 0 says, never into a new issue of its own. A backlog that grows while you work is the failure this whole method exists to prevent.
Previous: Shape the ticket for the agent | Home | Next: The cascade
Start
The method
- 4-4a. Scripts, not instructions
- 5-6. Rework and concurrency
- 14a-14h. Field notes from parallel agents
Brain and the test queue
How the plugin runs it
- Shaping a Ticket
- Models and the Cascade
- Adversarial Review
- Review Rules
- Holdout Check
- Measuring a Batch
- Retro
Reference