Meal Planner

Workflow

Step 1: Generate a draft

brados mealplan generate

Parse the response. Present the plan grouped by day:

Here's your meal plan for the week:

**Monday**
- Breakfast: Overnight Oats
- Lunch: Chicken Wraps
- Dinner: Shrimp Scampi

**Tuesday**
- Breakfast: ...
...

Ask: "How does this look? Want me to change anything?"

Step 2: Iterate on feedback

Brad will reply with change requests in natural language like:

• "swap Tuesday dinner for something with chicken"
• "I don't want red meat on Monday"
• "remove Wednesday lunch, I'll eat out"
• "too much effort on Thursday, make it easier"

For each round of feedback, send it through the critique endpoint:

brados mealplan critique <session_id> "<Brad's feedback verbatim or lightly cleaned up>"

Parse the response. Show:

1. What the AI changed (from the explanation field)
2. The full updated plan (same day-grouped format as Step 1)

Then ask: "Anything else you'd like to change?"

Repeat until Brad says it looks good / approves / says "finalize" / "looks good" / "perfect" / etc.

Step 3: Finalize

brados mealplan finalize <session_id>

Confirm: "Meal plan finalized!"

Step 4: Shopping list (SEPARATE MESSAGE)

brados shoppinglist generate <session_id>

Send the shopping list as its own standalone message, formatted for easy copy/paste:

**Shopping List**

**Produce**
- 2 cups cherry tomatoes
- cilantro
- 3 lemons
- ...

**Dairy & Eggs**
- 1 cup shredded mozzarella
- ...

**Meat & Seafood**
- 1 lb shrimp
- ...

Rules for the shopping list:

• Use the display_text field for each item (it's pre-formatted with quantity + unit + name)
• If display_text is just the ingredient name (no quantity), show it as-is
• Group by section, in the order returned (already sorted by store aisle)
• Skip empty sections

Resuming an existing plan

If Brad asks to "check the current plan" or "what's the meal plan", fetch it:

brados mealplan latest

If a plan exists and is not finalized, present it and ask if they want changes. If finalized, say it's already locked in and offer to generate a new one. If null, offer to generate a fresh plan.

Checking available meals

If Brad asks what meals are available or wants to know what options exist:

brados meals list

Group by meal_type (breakfast/lunch/dinner) and present as a clean list with names only.

Error handling

• If a command fails, check stderr for the JSON error and explain it simply
• "Session not found" → the plan may have expired, offer to generate a new one
• "Insufficient meals" → not enough meals in the database for a full week
• Auth errors → ask Brad to check the App Check token