planlisted

# Plan ## What this skill is — and isn't | Skill | Question it answers | Output | |---|---|---| | `vd:brainstorm` | "How should I approach this — what are the options?" | Decision brief with 3+ approaches | | `vd:research` | "Which of these known options should I pick?" | Comparison report with citations | | **`vd:plan`** | **"Given the chosen approach, what are the steps to ship it?"** | **Phased plan: `plan.md` + `phase-XX-*.md`** | | `vd:cook` (or manual impl) | "Execute the plan." | Code changes | Plan converts a *decided* approach into a *sequenced* implementation. If the approach isn't decided, stop and run `vd:brainstorm` first. A plan that opens with "we should consider whether to use X or Y" is a brainstorm in disguise — kick it back. ## Hard rules 1. **No code, no scaffolding, no source edits.** Only plan files. If the user pushes for implementation, hand off to `vd:cook` or implement separately. 2. **One decided approach in, one plan out.** If the input is ambiguous about *what* is being built, ask — don't guess and write a plan for the wrong shape. 3. **Phases are independently reviewable units.** Each phase should be reviewable/mergeable on its own — not "step 4 of 12 with no working state in between." A phase that can't ship standalone is two phases. 4. **Concrete, not aspirational.** Every phase names the files it touches, the steps in order, and the criteria that prove it's done. "Implement auth" is not a phase. "Add `auth/middleware.ts` validating JWT si