to-plan

Distil the chat discussion so far (or a roadmap item) into `.task/task/<slug>.md` — `## Description` **and** `## Plan` (Goal/Touches/Logic steps), plus `## Tests` when the testing policy calls for it, and the standard `## Execution` block. The deepest of the three capture skills (`to-task` / `to-plan` / `to-roadmap`): use it when you know enough about the approach to hand straight to implementation, or run it again on a `to-task`-only file to add the Plan in place. The slug is the filename; the artifact path is the handle. **Input:** `$ARGUMENTS` — optional. Recognized forms: - (empty) — draft from the chat discussion so far, or continue a task this conversation is clearly about (see Step 1). - `<slug>` or a path to an existing `.task/task/<slug>.md` — target that file directly. - `<roadmap-slug>` or `<roadmap-slug>#<N>` — open from that roadmap item instead of the chat. - anything else — free-form context to fold into the draft alongside the chat discussion. **Format contract:** [docs/contract.md](../../docs/contract.md) is the single source of truth for the output structure — read it if anything below is ambiguous. ## Step 0: Setup gate Check whether `.task/config/config.md` exists — resolve the pipeline root via `skills/_lib/resolve-ws.sh` (source it; it exports `AI_DIR`). - **Absent → inline setup.** Run the inline setup gate exactly as [`skills/to-task/SKILL.md`](../to-task/SKILL.md) Step 0 does (detect stack → ONE `AskUserQuestion` confirmation with **Accept** / **...