to-tasklisted

Distil the chat discussion so far (or a roadmap item) into `.task/task/<slug>.md` — `## Description` only, no `## Plan`. Lightest of the three capture skills (`to-task` / `to-plan` / `to-roadmap`): use it to record the "what and why" before implementing directly, or before `to-plan` later. The written file is the handle — no active-task pointer, no separate execution skill; a fresh session implements it by reading `## Execution`. **Input:** `$ARGUMENTS` — optional. Recognized forms: - (empty) — draft from the chat discussion so far. - `<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. ## 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" # sourcing runs find_ai_dir → sets 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" ``` The helper walks `task.root` git config when that path already holds a `.task/CLAUDE.md` → ancestor `.task/CLAUDE.md` (the walk stops at the top of this project, so it never claims a neighbouring one's `.task/`) → `dirname(git-common-dir)/.task` → `$CLAUDE_PROJECT_DIR/.task` when that path already holds a `CLAUDE.md` → `./.task`. Use `${CLAUDE_PLUGIN_ROOT}` — a bare `skil