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 ## Execution pointer. 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 is the single source of truth for the output structure — read it if anything below is ambiguous.

Step 0: Setup gate

Resolve the pipeline root, then check whether its CLAUDE.md exists:

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"

Use ${CLAUDE_PLUGIN_ROOT} — a bare skills/… path resolves against the user's project cwd, where it does not exist, and an unset $AI_DIR would send Step 7's mkdir -p "$AI_DIR/task" to the filesystem root.

Once .task/CLAUDE.md exists, every artifact path in this skill is under that resolved $AI_DIR, never the cwd (the inline setup below is the one exception — it runs before a root exists) — .task/task/<slug>.md below is shorthand for $AI_DIR/task/<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.

• Absent → inline setup. Read ${CLAUDE_PLUGIN_ROOT}/skills/_lib/setup.md and follow it (detect stack → write $AI_DIR/CLAUDE.md from its template → record git config --local task.root → exclude .task → report what was written). No confirmation chip: the file is written first and edited afterwards if a detected value was wrong. setup.md is the single source of truth for the sub-steps and for the file template; do not defer to a separate setup command and do not restate the template here. Then continue to Step 1 with the original $ARGUMENTS unchanged.
• Present → leave it alone. It is user-owned; only task.root and the .git/info/exclude line are restored when missing.

There is no full-scan validate call here — the file this run writes is validated after the write (Step 7), and pre-existing artifacts are checked on demand with validate.sh all, never as an entry gate.