triagelisted

# Triage — Read-Only Verdict Phase Investigate-only pickup lane for a backlog card. The thinking runs in the `triage` subagent (`agents/triage.md`, `model: opus`); this skill is the dispatch shell + absorption protocol. The agent traces root cause cold, sizes the fix, lands one verdict artifact; the fix is a later phase that inherits the verdict. ## Arguments | Invocation | Behavior | | --- | --- | | `/super-bootstrap:triage BUG-012` (any `BUG/DEBT/GAP-###` ID) | Dispatch the `triage` subagent on that card. | | `/super-bootstrap:triage` (bare) | List open backlog rows with no verdict file yet; the user picks one, then dispatch. | ## Execution 1. Resolve the card: the ID's `### {ID}` heading exists under `docs/backlog.md` § Open. Missing → report "no open row {ID}", stop. A verdict file for this ID already in `docs/work/triage/` → surface its path instead of re-dispatching (re-triage only on explicit user ask; delete the stale verdict file first). 2. Dispatch: `Agent` tool, `subagent_type: "triage"`, prompt = the card ID + today's date + the gateway-aligned problem-aim when framing sharpened or corrected the card claim (premise / problem / scenario only). Exclude cause theories and fix preferences (bias-input exclusion) — the aligned aim is the user-validated target, not a prior; the card row carries the frozen claim. 3. Absorb the agent's report (`agents/triage.md` § Reporting): - **DONE / DONE_WITH_CONCERNS** — relay verdict + path. scope.md → post the route line off