task-triage

# Task Triage — judge, dispatch, verify (the human keeps the last switch) A task ledger grows faster than it drains because filing is the cheapest action anyone can take. This skill is one **cycle** of a loop that drains it — not by implementing faster, but by putting judgment first: every open task is re-read against the code and its own start condition, and only what survives is dispatched. `resolved` / `rejected` / `withdrawn` / `obsoleted` count as success exactly like `done`. Roles (decided 2026-08-17, ADR-0043): | Role | Who | Does | Never does | |---|---|---|---| | **Judge** (this skill) | the triage session (Fable-tier) | premise check, worth check, better-solution check, condition check → verdict; writes kickoff packets; independently verifies build output; keeps the books | files tasks on its own initiative, confirms a drop alone, merges to main, touches rules / ADR / hooks / published artifacts unattended | | **Build** | a fresh session per task (Opus-tier), in a git worktree | Phase 0 premise re-check → implement → commit on the task branch with the evidence in the commit body | changes acceptance conditions, merges, pushes, edits the ledger | | **Human** | the owner | direction for tasks that need it, batch answers to the digest, the merge word | watches individual sessions (attention is the scarce resource) | The mechanism (Workflow tool, `/loop`, cron, Herdr) is the substrate's; this skill covers only what to judge and how to keep the loop from running away...