← ClaudeAtlas

roadmap-to-workflowlisted

Fan an approved `.task/roadmap/<slug>.md` out to a dynamic Workflow — parallel planning, serialized implementation, dependency-ordered waves.
SpaiR/task-pipeline · ★ 7 · AI & Automation · score 78
Install: claude install-skill SpaiR/task-pipeline
Drive an approved roadmap through a dynamic Workflow. This skill collects the roadmap's unchecked items, sorts them into dependency-ordered **waves**, then invokes the **plugin-shipped Workflow driver** (`skills/_lib/roadmap-driver.js`, via the Workflow tool's `scriptPath`) that, within each wave, plans all items in parallel and then implements, reviews, and ticks them off one item at a time in the shared working tree. It does **not** hand-roll that fan-out itself, and it does **not** author the Workflow script — the driver is a static file, inspectable at any time, parameterized only through `args` (Step 2). If the Workflow tool isn't available, it falls back to running items serially by hand, in the same dependency order (Step 2). **Per-item model control.** Each roadmap item may carry a `**Model:**` hint (`haiku | sonnet | opus`); the driver passes it to that item's implement agent as `opts.model`, and scales the plan stage down for lightweight items (a `haiku`-hinted item is planned by sonnet at low effort; everything else by opus). The review agent ignores it — `task:code-reviewer` pins its own model, so a `haiku` item never gets a `haiku` review. **Per-item execution is a three-agent split by default — opus plans (sonnet for `haiku`-hinted items), the item's model implements and commits, `task:code-reviewer` reviews and commits its fixes on top; a fourth, cheap driver stage then ticks the roadmap checkbox (Step 2).** **This skill *is* the opt-in** for the Workflow to