implementlisted

Work the open tasks of the plan one at a time, in dependency order: `tasqx_list_tasks` under the project (`tasqx_list_projects`) if the plan lives there, else the `plans/` file. For each task: 1. `tasqx_start_timer` and annotate the approach. 2. Pick the tier and dispatch: - Tiered mode: run `skills/tier/route.py` once for the step, exactly as `hooks/tiered.md` shows: ```bash python3 "${CLAUDE_PLUGIN_ROOT}/skills/tier/route.py" <<'EOF' {"task": "<the task in one or two lines>", "steps": [{"id": 1, "title": "<step>", "brief": "<files, the change>"}]} EOF ``` then dispatch `1337:builder` at the tier it printed. - Otherwise, pick the tier yourself per `hooks/orchestrator.md`'s ladder (haiku/sonnet/opus). The builder brief asks for `/1337:tdd` red-green-refactor. 3. Verify with `1337:checker`. 4. `git diff`, then `/1337:review` in spec mode against the task's spec. 5. Annotate what was delivered. 6. Commit the task. On checker `FAIL`: retry once, one tier up from the routed/chosen tier, never twice, never for a step already at Opus; if it fails again, stop and hand off to `/1337:diagnose`. Never `tasqx_complete_task` without the user's acceptance. One routing call licenses exactly as many builder dispatches as it routed steps — route each task on its own rather than batching several under one call. Review the diff before moving to the next task; nothing after a dispatch skips straight to another dispatch or a commit. Ou