cooklisted

# cook Implement the approved scope with the smallest loop that can establish trust. ## Workflow 1. Read `plan.md` when present. Confirm the next unchecked item and its acceptance criteria. Use `scout --repo` only when touchpoints or current behavior are uncertain. 2. Edit the scoped code. Dispatch an implementer or tester only when isolation, size, risk, or tests-first work makes it useful; send a compact inline contract and changed-file context, not a generated brief file. 3. Run focused verification, then inspect the diff. Request independent review for public contracts, security/data/migration/concurrency risk, unfamiliar surfaces, or an explicit review request. Handle `APPROVE`, `REQUEST CHANGES`, or `BLOCK` before claiming completion. 4. Update the plan's checkbox/status when a plan exists. Write or append `plans/YYMMDD-{slug}/implement-notes.md` with completed scope, changed files, commands/results, material decisions or deviations, review verdict when present, and residual risk. This is the only cook artifact. 5. Stop for a blocker, failed verification, or a decision that changes the Design Contract. Keep commits, push, and release as explicit user choices. For a clear standalone request, create `plans/YYMMDD-{slug}/implement-notes.md` only after the change is verified. Do not generate phase briefs, phase evidence, implementer reports, implementation-note copies, or review files.