← ClaudeAtlas

cooklisted

Execute a plan (or a small task) phase-by-phase: implement → verify → test → review → update status. Use after `vd:plan` to ship the plan, or directly for tight tasks (`--quick`). Default stops at review gates between phases; pass `--auto` to run straight through, `--quick` for sub-plan tasks, `--tdd` for tests-first.
vanducng/skills · ★ 0 · AI & Automation · score 76
Install: claude install-skill vanducng/skills
# Cook ## What this skill is — and isn't | Skill | Question it answers | Output | |---|---|---| | `vd:brainstorm` | "How should I approach this?" | Decision brief | | `vd:plan` | "Given the approach, what are the steps?" | Phased plan | | **`vd:cook`** | **"Execute the plan — turn the spec into code."** | **Code changes, tests passing, plan status updated** | Cook **implements**. It does not design. If during cooking you find the plan is wrong, **stop** and kick back to `vd:plan` (or `vd:brainstorm` if the approach itself is wrong) — don't silently redesign while typing. ## Hard rules 1. **One phase at a time.** Don't start phase N+1 until phase N's success criteria pass. 2. **No new design decisions in code.** If a step requires a choice the plan didn't make → stop and ask. Don't pick silently. 3. **Compile/type-check after every file**, not at end of phase. Fail fast. 4. **Tests pass before review.** Don't ask for review with red tests. 5. **Plan status reflects reality** — update phase frontmatter and `plan.md` after each phase, never at the end. 6. **Outside review per phase.** Spawn a subagent reviewer at least once before declaring a phase done; self-review is not enough. ## Modes | Mode | When | Behavior | |---|---|---| | `--quick` | Tight scope, no plan exists, single-file change | Skip plan-loading; treat task as a single phase. Still verify + test before done. | | **default** | Standard execution of an existing plan | Phase loop with **review gate** between p