cook

Execute phased code changes with gated implement, verify, test, and review steps.

5|Updated May 2, 2026
One-click install
npx skills add https://github.com/vanducng/skills --skill cook-vanducng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cook
Source: https://github.com/vanducng/skills/tree/main/skills/cook
Command: npx skills add https://github.com/vanducng/skills --skill cook-vanducng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Orchestrates phased execution of plans by guiding implement → verify → test → review steps, with gated transitions to ensure quality before shipping code.

Core Features & Use Cases

  • Phase-driven execution: implement, verify, test, and review with status updates.
  • Mode controls: --auto, --quick, --tdd, and --no-test to tailor the run.
  • Pre-flight, conform, implement, verify, test, and review steps with plan status updates and DoD validation.
  • DoD-based gate: final goal gate evaluation using scripts/eval-dod.sh.

Quick Start

Run vd:plan to generate a plan, then run cook to execute that plan through its phases.

Frequently Asked Questions about cook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute a development plan step-by-step with phase gates?

To execute a code-change plan step-by-step, this Skill orchestrates phased work cycles through conform, implement, verify, test, and review steps, enforcing phase boundaries with gated transitions to ensure code quality before shipping.

What is phased workflow automation for code changes?

Phased workflow automation for code changes is a process that guides stepwise progress through development phases, updating plan status and validating Definition of Done criteria via scripts between transitions to prevent unverified code from advancing.

Can I skip tests during automated code execution?

Yes, you can skip tests during automated code execution by using the --no-test mode flag, or apply --quick, --tdd, and --auto flags to tailor the phased workflow run behavior.

How do I start phased execution after generating a plan?

To start phased execution after generating a plan, run the cook command; it reads the plan status and automatically guides the work through pre-flight, conform, implement, verify, test, and review steps.

What is the best way to verify code changes before shipping?

The best way to verify code changes before shipping is using a DoD-driven gate evaluation, which validates the final goal of the plan using scripts/eval-dod.sh to ensure all conform, implement, testing, and review criteria are met.