AI meal planner: a week of dinners that fit the fridge, the clock, and the allergy list

Plan from constraints, then fill nights

Start with the week you have. Three late nights. One night with a guest. One night of leftovers by policy. Put those facts in the generate notes: "Mon-Wed 30 minutes, Thursday roast chicken, Friday fried rice from Thursday, Saturday guest, no shellfish." Taste Profile already holds diet, allergies, equipment, servings, spice, and units. The note holds the calendar. An AI meal planner that ignores the calendar writes a 90-minute braise for Wednesday and you will order noodles.

Generate one anchor protein or one pot of legumes, then ask for two derivative dinners. Roast chicken on Thursday becomes chicken-rice soup and chicken salad if you carve with intent. A pot of dal becomes dal and rice, then dal-stuffed wraps with a fresh salad so you are not eating identical bowls. The generator is good at this if you say "same base, different starch and vegetable." It is bad at this if you say "meal plan" with no leftover policy.

Shop once from the combined ingredient lists. Use the recipe scaler if Thursday is four servings and Saturday is six. Scaling is not always linear for fond and for oven time. A larger roast needs more minutes, not a proportional fantasy. The oven-temperature converter helps if a Saturday recipe arrived in gas marks and your oven door is Fahrenheit.

Leftover physics and the FSIS clock

USDA FSIS leftover guidance is specific. Refrigerate within 2 hours of cooking (1 hour if the ambient temperature is above 90 °F). Use cooked leftovers within 3 to 4 days. Reheat to 165 °F. A meal plan that parks chili on the stove until bedtime is a safety plan, not a cooking plan. Cool in shallow containers. Label the day. The Cook Journal photo of Sunday's chili is cute. The date on the lid is the part that matters on Wednesday.

Carryover cooking on Sunday's roast still applies. Rest the meat, carve, then chill the portions you will not eat tonight. Leaving a whole chicken in a 165 °F cavity to cool on the counter for three hours is the two-hour rule failing in slow motion. Slice. Spread. Fridge.

Freezer nights extend the plan. Soups, dal, and seasoned ground meat freeze better than fried rice (the rice dries) and better than salads (the greens collapse). If the generator suggests five fried dishes for freezer meal prep, reject the card. Ask for braises, beans, and sauces. Reheat with a splash of water and a fresh vegetable so week-three dinner still has a crisp edge.

Nutrition across the week, not per pretty plate

The Dietary Guidelines for Americans talk in patterns: vegetables, fruit, grains, protein foods, dairy or fortified alternatives. A week of high-protein, low-vegetable skillet meals can hit a protein target and miss the pattern. When you generate, add "include a vegetable that is not a garnish" on at least four nights. Log the week in the diary. Look at fiber and protein together. FoodData Central will show you that a cup of cooked lentils is a different food from a cup of cooked white rice. Plan accordingly.

TDEE from the calorie calculator (Mifflin-St Jeor, PubMed 2305711, times activity) is a daily energy budget. Meal planning assigns that budget to cooking you will do. If Thursday is a restaurant, log it as a restaurant. Do not "save up" by skipping lunch unless that is a pattern you chose on purpose. Skipping lunch and then frying extra potatoes at 9 p.m. is a common way a meal plan's math dies.

Allergen planning is a shopping problem. If wheat is on the list, the week's sauces need labeled gluten-free bottles in the cart, not a hope that the generator picked tamari. AI can miss wheat in sauces. Put the bottles on the list yourself. Verify every label. The meal plan is not a clinical meal service.

Plan from the fridge photo when the week is already underway

Wednesday at 6:15 p.m. is a bad time for a seven-day spreadsheet. Photograph the fridge shelf and the onion bowl. Use the pantry flow (what can I cook with these ingredients). Generate one dinner that spends the wilting spinach and the half-can of coconut milk. That is meal planning in the only sense that prevents waste. The USDA Keep Food Safe page still applies: perishable food in the danger zone is not a "use it up" candidate. If the chicken has been out for three hours, the plan is the bin.

A written list of remaining cooked food helps the generator. "400 g cooked rice, 250 g roast chicken, one bunch scallions, eggs." Fried rice, chicken soup, or a frittata are all legal. Pick the one that matches the time cap. Cook Mode timers keep the rice from burning while you chop the scallions. Mise en place for a leftover dinner is still mise en place. The leftover is an ingredient, not a finished thought.

Barcode the milk and the yogurt so the dairy you actually have is in the diary and in your head. Open Food Facts will name the product. Your meal plan should not assume a liter of milk you finished on Monday.

Batch the tedious parts. Keep one fresh element.

Sunday can be beans, grains, a sauce, and a tray of roasted vegetables. Monday through Wednesday you generate "assemble" recipes: grain bowl, taco filling, soup with the beans. The Maillard you already paid for on the sheet pan does not need to be repeated every night. A fresh element (a lime, a handful of herbs, a cucumber, a fried egg) keeps the plate from tasting like a cafeteria. Ask the generator for that fresh element by name if the first card is all beige.

Air-fryer nights are for the leftover protein that needs a crust again: tofu cubes, chicken thighs, roasted potatoes. 375 to 400 °F, single layer, shake once. The meal plan should not put three air-fryer mains on the same evening if you own one basket. Sequence them, or pick two stove nights.

Skill in Taste Profile should match the week's ambition. A beginner week with three knife-heavy stir-fries will slip. Generate "one-pot," "sheet-pan," and "soup" until the knife work feels cheap. Then add a wok night.

Guests, diets, and two-track pots

When diets diverge, plan a shared base and two finishes. A pot of rice and a pot of beans can take cheese and chicken on one side and salsa and avocado on the other. Generating two fully separate menus for one kitchen on a Tuesday is how you burn out. Put the constraint in the note: "base vegan, optional feta and chicken for omnivores." The allergen list still wins. If a guest has a peanut allergy, the satay night is a different week.

Kids and spice: generate mild, then put chili crisp on the adult table. Do not invent a second protein if the mild version is the same chicken with the chili left off. Time is the scarce ingredient.

If you track macros, assign the guest night a looser target and log it. The meal planner's job is that food hits the table hot. The diary's job is that Friday is not a mystery.

Sunday night is a review, not a moral

What got cooked. What got thrown away. What you reordered because the plan was fantasy. Feed those three facts into next week's notes. If cilantro died twice, stop buying cilantro. If the 30-minute cards still ran 50 minutes, your mise en place is the bottleneck, or the generator is lying about time. Time the actual onion chop once. Then believe the clock.

Storage audit: anything older than the FSIS 3 to 4 day window leaves the fridge. Anything in the danger zone from a lunchbox that sat in a car is not "tomorrow's lunch." USDA Keep Food Safe is the rule set. Your nose is a backup, not a lab.

Credits: generate the week's anchors on Sunday, then use pantry-photo generates for midweek surprises. Do not generate seven full recipes you will not cook. Three anchors and two flex nights will beat a beautiful unused plan.

Questions

Sources

• USDA FSIS, Leftovers and Food Safety
• USDA, Keep Food Safe
• Dietary Guidelines for Americans
• USDA FoodData Central
• Mifflin-St Jeor equation (PubMed 2305711)
• FDA, Nutrition Facts Label