ck:cook

ck:cook — Budget-Aware Implementation Pipeline

Cook implements code and performs a compile/syntax check. ck:test owns tests and ck:quality owns quality review; Cook orchestrates either only after user consent.

Modes are mutually exclusive; Standard is the default:

• Standard — ask for the phase's test and quality choices, then auto-continue after the selected checks finish.
• --fast — default the current phase to no unit tests and no quality gate unless explicit check flags are supplied.
• --hard — default both checks to yes and require human confirmation after the selected checks and before the final push.

Composable flag:

• --tdd — select tests=yes and require a RED_READY artifact before implementation.
• --tests / --no-tests — select whether ck:test --unit creates/runs unit tests for the current phase.
• --quality / --no-quality — select whether ck:quality --gate runs for the current phase.
• --checks-all-phases — apply explicitly supplied test/quality choices to every remaining phase; without it, ask again at the next phase.

Reject contradictory flag pairs. No old single-file JSON or mixed-format compatibility is supported. Markdown plan.md remains a separate input format.

Step 0.5 — Phase Checkpoint

Before reading implementation files or activating each phase, resolve two independent choices: Unit tests: yes/no and Quality gate: yes/no.

• Honor explicit flags without asking. In Standard mode, ask one concise question containing both choices that remain unresolved. Do not silently infer consent from a previous phase unless --checks-all-phases was supplied.
• In --fast, unresolved choices default to no. In --hard, unresolved choices default to yes.
• State the token/risk tradeoff briefly: tests catch behavioral regressions; quality checks architecture and maintainability; skipping either saves tokens but reduces assurance.
• Record the decision before activation/completion in a separate phase-state write. For JSON, a skipped gate requires quality.status: skipped_by_user and quality.decision: user_confirmed_skip; it is never approved. Later complete the phase and master in separate phase-first/master-second writes so receipt hooks validate persisted consent. For Markdown, append [quality: skipped_by_user; decision: user_confirmed_skip] to that phase's checkbox line. A skipped test run remains not_started with a note that the user declined it.
• If tests=yes without --tdd, run /ck:test --unit <phase-file> after implementation and the Build Gate. If --tdd, use the RED/GREEN handoff described below.