to-roadmaplisted

Fix a **multi-task initiative** (phases, dependencies, or more than a couple of atomic steps) into `.task/roadmap/<slug>.md`. Multi-task counterpart to `/task:to-task` / `/task:to-plan` (which each fix one task). Depth is fixed: one roadmap file, flag-free. **Input:** `$ARGUMENTS` — a rough description of the initiative, or a reference back to a prior discussion in this conversation ("build a roadmap from what we discussed"). **Format contract:** [docs/contract.md § Roadmap file format](../../docs/contract.md#roadmap-file-format-taskroadmapslugmd) is the single source of truth for the output structure. This file describes the authoring flow that produces it. ## Instructions ### Step 0: Setup gate Resolve the pipeline root, then check whether its `CLAUDE.md` exists: ```bash source "${CLAUDE_PLUGIN_ROOT}/skills/_lib/resolve-ws.sh" # exports AI_DIR echo "$AI_DIR" # the resolved root — use this value verbatim in every artifact path below [[ -f "$AI_DIR/CLAUDE.md" ]] || echo "CLAUDE.md not found" ``` **Every artifact path in this skill is under that resolved `$AI_DIR`, never the cwd** — `.task/roadmap/<slug>.md` below is shorthand for `$AI_DIR/roadmap/<slug>.md`. A cwd-relative write from a subdirectory or a linked worktree would create a second `.task/` that `validate.sh` (which resolves `$AI_DIR` itself) never sees. - **`CLAUDE.md not found`** → `/task:to-roadmap` is intake-capable: read `${CLAUDE_PLUGIN_ROOT}/skills/_lib/set