Prep

Read ~/.claude/chef/config.md. Extract:

• people — people eating each meal
• prep_days — days to prep for (default: 4)
• prep_extras — extra portions per meal beyond people (default: 0, e.g. 1 for packed next-day lunches)
• health_goals — weekly macro/diet target
• dietary — hard constraints (never violate)
• preferred_stores — passed to grocery-check
• prep_time — available prep session time (default: 2h30)

Portion formula:

portions_per_meal = people + prep_extras
total_portions    = prep_days × portions_per_meal
anchor_batch      = portions_per_meal × 2

Show the calculated targets at the top of your output:

Prep target: 4 days · 3 portions/meal (2 people + 1 packed lunch) · 12 total
Structure: 1 anchor ×6 + 2 lighter ×3

Step 2: Grocery Check

Invoke chef:grocery-check (integrated mode — returns deals data, no formatted output).

Use deals to bias protein selection toward what's on sale. A 40%+ deal on a protein should strongly influence the anchor batch choice.

Step 3: Plan Meals

Constraint priority (when conflicts arise):

1. dietary — hard, never violate
2. health_goals — hard for the week's balance, soft for a single meal
3. use-up ingredients — soft, use them unless they conflict with #1 or #2
4. grocery deals — nice-to-have, can be overridden

Structure:

• Anchor batch (anchor_batch portions) — highest effort, must reheat well. Braises, grain bowls, soups, roasted protein + veg.
• Lighter recipes — portions_per_meal each, faster, complement the anchor

Health balance across the week:

• Vary proteins (don't repeat the same protein every day)
• At least one plant-forward meal
• At least 3 distinct vegetables across the week
• Avoid carb stacking (pasta + rice + bread in same week)

Format per proposed meal:

1. **[Name]** — [portions] · [time] · reheats: [yes/well/poorly]
   Protein: X · Veg: Y, Z · Base: W
   On sale: [ingredient ↓XX%]  (if applicable)
   Uses up: [ingredient]  (if applicable)

Be opinionated — recommend the plan you'd pick and explain why.

Step 4: Component Map

Every component listed MUST appear in ≥2 meals. If no genuine reuse exists for a recipe, note it as "standalone" — do not fabricate reuse.

## Component Map

| Component | Prep once | Used in |
|---|---|---|
| Roasted sweet potato | 800g, 400°F (200°C) 25min | Meal 1 bowl + Meal 2 side |
| Quinoa | 300g dry | Meal 1 base + Meal 3 addition |
| Poached chicken | 600g | Meal 2 sliced + Meal 3 shredded |

Step 5: Shopping List

Grouped by store (preferred_stores). Include all ingredients — mark accordingly:

• (already have) — from use-up input
• (pantry check) — common staples

Step 6: Prep Session Timeline

Timed order for the prep session, using prep_time from config (default 2h30). Start longest tasks first; run independent tasks in parallel.

## Prep Session (2h30)

**0:00** — Preheat oven to 400°F (200°C). Start braise (45 min unattended).
**0:10** — Prep + roast veg tray (25 min).
**0:15** — Cook grains (20 min).
...
**2:15** — Label + refrigerate. Note what freezes vs. fridge only.

Step 7: Save Session Files

Save to {sessionDir}/{YYYY-MM-DD}-prep/:

• plan.md — meal plan + component map
• shopping.md — shopping list by store
• timeline.md — prep session order
• metadata.md — session context:

---