meal-planning

Meal planning with mealforge

Plan meals collaboratively in chat, then publish the finalized plan to the mealforge app. A plan is any set of 1+ meals — a full week of dinners, a weekend of brunches, breakfast-lunch-dinner-snacks, or one special meal. Each meal is typed breakfast, lunch, dinner, or snack. Planning is conversation — as much back-and-forth as it takes. Publishing is a command — it happens exactly once, only when the user says so, and always via the two-step flow: save each recipe with create_recipe, then assemble the plan with push_meal_plan using recipeIds only.

The plan lifecycle

Plans move through three states, and the household cooks from exactly one active plan at a time:

• upcoming — pushed but not started; plans queue here.
• active — the plan being cooked from right now. Its grocery list is the one in the app. A brand-new push becomes active automatically only when nothing else is active.
• completed — cooked through; browsable history.

Lifecycle moves are user commands, not your judgment calls: complete_meal_plan when they say they're done ("we finished the week", "wrap up this plan"), activate_meal_plan when they pick what's next. Activation fails while another plan is active — complete that one first (confirm with the user).

When to use

• The user wants to plan meals ("let's plan next week", "plan me three breakfasts", "meal plan time")
• The user revises a pushed plan ("swap the salmon", "add a couple of snacks to the plan")
• The user tells you to push/send the plan to mealforge
• The user wants to switch plans, finish a plan, or bring back a favorite plan

How to apply

1. Gather context before proposing anything

• get_active_meal_plan and list_meal_plans (limit 6) — see what's cooking now and what was cooked recently; don't repeat recent meals unless asked. Each meal's cookedAt (null = not cooked yet) is the household's check-off, so you can answer "what's left to cook this week?".
• If the user wants something they've had before ("one of our favorites", "that carnitas"), find it with list_favorites or search_recipes, confirm with get_recipe, and remember its recipeId — reuse the id at push time instead of recreating the recipe.
• For "one of our favorite plans", use list_meal_plans with favoritesOnly: true and rebuild from its recipeIds.