interview

# Interview Interview extracts **want**: outcome / user / success / constraint / out of scope, confirmed with an explicit yes. `--grill` walks an existing plan or idea. `--wayfinder` charts a multi-session decision map. Those are modes of this skill, not other skills - do not look for `vd:wayfinder`. 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 hypothesis + confidence before asking.** Attach your best guess and a recommended answer. Why: reacting is faster than generating from scratch, and a visible guess is easy to correct. 3. **Never ask a fact you can look up.** Repo layout, current stack, existing APIs, prior ADRs - read them. Why: the user's job is decisions, not research. 4. **Explicit yes on a concrete restate.** "Sounds good", "whatever you think", and silence are not yes. Why: a hollow yes becomes the wrong PR. 5. **Out of scope is mandatory.** Half of misalignment is silent disagreement about what is *not* being built. 6. **No options, no plan, no code** until the restate is confirmed. Why: options widen the search; thi...