This example demonstrates a complete /cook workflow from feature request to cooked output.
You have a todo app and want to add a "due date" feature to tasks.
- CLAUDE.md - Project context file (required for best results)
- feature_request.md - The feature we want to cook
- cooked_output.md - What
/cookproduces
# 1. In your project, ensure you have CLAUDE.md
cat CLAUDE.md
# 2. Invoke /cook with your feature
/cook Add due date field to tasks with reminder notifications
# 3. Review the cooked artifact
# Claude will produce output similar to cooked_output.md- Phase 0: Claude reads your CLAUDE.md and extracts project rules
- Phase 1: Product Chef evaluates scope and value
- Phase 2: UX Chef reviews user experience
- Phase 3: Architect Chef designs technical approach
- Phase 4: Engineer Chef creates implementation plan
- Phase 5: QA Chef defines test strategy
- Phase 6: Security Chef audits for vulnerabilities
- Phase 7: Final artifact is produced
- Good CLAUDE.md = better results
- Specific requests = specific output
/cookstops you from coding too early- The artifact is your implementation guide