threnody-tasklisted

# Threnody task orchestration **Execution phase** after planning — see **`threnody-plan`** for plan-only vs plan-then-execute routing. Use this skill for **planning + host wave execution** without the full swarm persistence contract (`swarm_id`, budget preview, resume checkpoints). ## When to use | Use `threnody-task` | Use `threnody-swarm` instead | |---------------------|------------------------------| | `plan_task` / `decompose_task` / `fleet_plan` | `execute_swarm` | | Host runs `host_spawn_waves` | Need `swarm_id`, telemetry, resume | | No budget preview token flow | Budget preview + `preview_token` confirm | | Single planning pass | Coordinator star rounds (delegate mode) | ## Workflow 0. Prefer **`threnody-plan`** first unless the user already approved a wave plan. 1. **`route_task(task)`** — tier, `execution_hint`, optional single `host_spawn`. 2. **Decompose** (multi-concern work): - Prefer `decompose_task(task)` (alias of `plan_task`). - Or `plan_task(task)` directly. 3. **Read `host_spawn_waves`** from the plan response. 4. **Execute waves in order** via host `Task`/`Agent`: - Agents within one wave may run **in parallel**. - Respect wave ordering (later waves wait for earlier dependencies). 5. **Reporting** — check `learning_report_contract.report_mode`: - **`batch` (default):** do **NOT** call `report_host_wave` per worker wave. Spawn waves; learning is captured automatically (PostToolUse hook) or passed in the single terminal call (`learning