task-triagelisted

Run one cycle of the task-triage loop over a repo's task ledger — judge every open task (verify its premise in code, check its start condition against the 照合先, decide whether it is still worth doing, look for a better solution), then dispatch the accepted ones to fresh implementation sessions and act as their independent judge until the branch is merged. Use when the user says 「残タスクを見て」「タスクを整理して」「台帳を回して」「dispatch して」「未マージある？」, invokes /task-triage, or when a task ledger has grown and nobody can say what is dispatchable. NOT for consolidating scattered task files into a ledger (task-stocktake), NOT for deciding a single build-or-not question (architect), and NOT for running a task yourself.
shimo4228/claude-harness · ★ 3 · AI & Automation · score 82

Install: claude install-skill shimo4228/claude-harness

# Task Triage — judge, dispatch, verify, merge (the human sets direction) 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 (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; merges what passed §4 ff-only and pushes; keeps the books | confirms a drop alone; files tasks on its own | | **Build** | a fresh session per task (Opus-tier) — by default a Claude Code **cloud session** on a `claude/` branch cloned from GitHub, running without the harness (the packet is its whole contract); a local worktree session (Agent tool / Herdr) only for the cases §3 names | Phase 0 premise re-check → implement → run the one review the packet names → commit on the task branch with the evidence in the commit body → push (cloud) | changes acceptance conditions, merges its own branch, edits the ledger, touches the gate (`.claude/verify.sh`, `.github/`, `.claude/settings.json`) | | **Human** | the owner | direction for tasks t