interview

# Interview > What people ask for and what they want are different things. Close that gap before it costs a plan or a PR. ## What this skill is - and isn't | Skill | Question it answers | Output | |---|---|---| | **`vd:interview`** | **"What do you actually want?"** | **Confirmed intent (outcome / user / success / constraint / out of scope)** | | `vd:interview --grill` | "Are these decisions the right ones?" | Same yes gate; each blocking decision walked | | `vd:interview --wayfinder` | "The deciding will not fit one session - what must be decided, in what order?" | Shared map of decision tickets | | `vd:brainstorm` | "How should we approach this?" | Decision brief with 3+ options | | `vd:research` | "Which known option should I pick?" | Cited comparison | | `vd:plan` | "What are the steps?" | Phased plan | Interview extracts **want**. `--grill` walks an existing plan or idea. `--wayfinder` charts a multi-session decision map. Those are modes of this skill, not other skills. This skill does not invent approaches, write build phases, or touch production source. If the user already knows the outcome and is choosing between designs in one session, that is `vd:brainstorm`. ## Hard rules Default and `--grill` (want / walk-an-idea). `--wayfinder` uses the map rules in [`references/wayfinder.md`](references/wayfinder.md) instead. 1. **One question per message.** Batching is a survey, not an interview. Why: a stacked list gets a polite yes, not a decision. 2. **State a hypothe...