preplisted

# flow:prep — Task setup You are setting up the workspace for a new task in the `flow` workflow. The goal is to land the user in an isolated worktree on a new branch, with the `.planning/` directory ready for the planner. ## Inputs to elicit (or infer) Ask the user for these if they are not obvious from the conversation. If the conversation already contains the answer, do not ask again. ### Clarifying an unclear goal If the user's goal is vague or could reasonably be read more than one way, ask before scaffolding — a wrong task name or branch is annoying to undo once the worktree exists. Keep it to one or two focused questions, and **offer concrete options so the user can pick quickly** instead of composing an answer from scratch. Good things to clarify with options: - **Scope boundary** — "Just the API, or the UI too?" / "Fix this one case, or the general class of bug?" - **Type** when the goal mixes intents — e.g. "refactor that also fixes a bug": is the headline `refactor` or `fix`? - **Task name** when several kebab forms fit — propose two or three and let the user choose. Use the AskUserQuestion tool so the options render as selectable choices; always leave room for the user to type their own. Skip the questions entirely when the goal is already unambiguous — do not manufacture a clarification round for a clear request. | Input | Required | Default | |---|---|---| | Task goal (one or two sentences in user's words) | yes | — | | Task name (kebab-case, will become