guide

# Guide This skill picks the next skill. It does not interview, plan, or edit source. Name one skill (plus a flag if needed), say why, and stop unless the user asks you to run it. ## Delivery spine One path: **interview → brainstorm → plan → cook → ship**. `vd:ultracook` runs the smallest slice of the same path. | If | Use | |---|---| | Who / why / success / out of scope is missing | `vd:interview` | | A plan or idea needs its decisions walked | `vd:interview --grill` | | Deciding will not fit one session | `vd:interview --wayfinder` | | Want is clear, how is not | `vd:brainstorm` | | Approach is picked | `vd:plan` → `vd:cook` → `vd:code-review` → `vd:ship` | | Something is broken | `vd:debug` → `vd:fix` | | Drive the whole thing | `vd:ultracook` | ## Three "just get it done" paths | Path | Pick when | |---|---| | `vd:cook --quick` | Tight, no plan, one surface. You will still verify and test. | | `vd:fix` | Known bug, narrow blast radius. `--quick` on cook covers similar ground. | | `vd:ultracook` (direct) | User asked to orchestrate and the task is trivial. Ultracook classifies; it should not open a goal-dir. | If two apply, prefer `vd:fix` for failures, `vd:cook --quick` for small builds, `vd:ultracook` when the user wants a conductor. ## Review lenses | Question | Skill | |---|---| | Ready to land? | `vd:code-review` (posts on a PR) | | Does it fit the codebase / is it slop? | `vd:code-review --refactor` (local) | | Can it read easier with behavior frozen? | `vd:...