cook-backend

name	cook-backend
description	Workflow orchestration for backend projects (API routes, services, models). Structured phases — Plan, Code, Review, Test — with memory-bank integration for session continuity.

Cook — Backend Workflow

Structured workflow for backend projects. Every non-trivial task flows through ordered phases.

Plan → Code → Review → Test

---

Memory Bank — Required for Every Session

At the start of EVERY session, read all files in memory-bank/:

1. projectbrief.md — Core requirements and goals
2. productContext.md — Problem and solution context
3. techContext.md — Technical setup and dependencies
4. systemPatterns.md — Architecture and design patterns
5. activeContext.md — Current work focus and recent changes
6. progress.md — Completed work and known issues

If memory-bank/ does not exist, create it with the files above based on what you learn from the codebase.

After completing work (end of Test phase or any stopping point), update:

• activeContext.md — What was done, current state, next steps
• progress.md — Mark completed items, add new known issues

This ensures continuity across sessions. Never skip this step.

---

[PLAN] Plan

1. Read requirements. Ask if ambiguous.
2. Identify affected routes, services, models, and migrations.
3. Break into subtasks. Define acceptance criteria.
4. Identify API contract changes (request/response shapes).

Output: Numbered plan with affected files and acceptance criteria. No code in this phase.