Meal Planner

Educational note, not medical or dietetic advice. This skill helps organize and structure food choices; it does not replace a registered dietitian, physician, or allergist. If you are managing a diagnosed condition (diabetes, celiac disease, kidney disease, food allergy, eating disorder history, or any other medically relevant dietary concern), validate your targets and food choices with a qualified professional before following any plan this skill produces.

Most people try to meal plan the wrong way: they sit down Sunday morning, scroll recipe apps for an hour, write out seven elaborate dinners, shop for ingredients that partly overlap and partly don't, cook three things Monday, abandon the plan by Wednesday when they are tired, and throw away $40 of wilting produce on Friday. The plan looked complete on paper. It was not a system.

The failure has two root causes. First, the plan treats every meal as an isolated event instead of as a node in a network of shared ingredients and batch-cooked components. Second, the plan tries to be a menu, not a template — and menus require re-invention every week while templates run on autopilot. This skill does it differently: it builds a small inventory of interchangeable components, assigns them to a repeatable weekly skeleton, derives the grocery list mechanically from that skeleton (collapsing ingredient overlap before you ever walk into a store), and encodes leftover logic so that Thursday's extra chicken is already spoken for on Saturday. The result is a plan that survives low-energy nights, households with mixed dietary needs, and the ordinary chaos of a busy week.

When to use / when not to

Reach for this skill when someone wants to stop deciding dinner nightly or needs a plan for mixed household dietary needs.

Do not use it when the need is calculating targets first (use nutrition-calculator).

Modes

Context Loading Gates

Before generating any plan, gather all of the following. Do not start the plan with blanks in this list — ask for missing inputs explicitly.

Person / Household

• [ ] Number of people eating the plan (and rough ages/life stage if relevant — active teenager vs. sedentary adult changes calorie scale significantly)
• [ ] Any hard dietary restrictions: allergies (note: if severe/anaphylactic, flag for allergist consultation), intolerances, religious/ethical prohibitions (halal, kosher, vegan, vegetarian)
• [ ] Soft dietary preferences: foods strongly disliked, preferred cuisines, texture aversions
• [ ] Cooking skill level (beginner / intermediate / confident) and willingness to try new recipes

Goals and Targets

• [ ] Primary goal: weight loss / muscle gain / maintenance / general health / no specific goal
• [ ] Daily calorie target (or "none set — use Quick-Start mode")
• [ ] Macro targets if any (protein / carbs / fat in grams or percentages)
• [ ] Whether targets are the same every day or differ on training vs. rest days

Logistics

• [ ] Days and meals covered by the plan (all 7 days? weekdays only? dinners only?)
• [ ] Which meals will be skipped, eaten out, or handled independently (work lunches that are bought, for example)
• [ ] Available prep time: is there a dedicated batch-cook window (e.g., Sunday 2 hours), or is this a cook-as-you-go household?
• [ ] Kitchen equipment available (instant pot / slow cooker / sheet pans / air fryer significantly affect what is efficient to batch-cook)

Budget and Shopping

• [ ] Weekly grocery budget (or "no hard limit")
• [ ] Preferred grocery store(s) or delivery service
• [ ] Pantry staples already on hand (oils, spices, condiments, canned goods, frozen items) — even a rough inventory prevents over-buying
• [ ] Whether store-brand / generic substitution is acceptable

Methodology

Phase 1 — Establish the Nutritional Frame

1.1 Set daily calorie and macro targets

If the person already has targets from an app, dietitian, or TDEE calculator, use those directly. If not and the mode is Quick-Start, use this working default as a starting point — it is not personalized, and adjustments after 2-3 weeks based on real-world response are expected:

• Protein: 0.8–1.0 g per pound of target bodyweight (lean muscle mass is an even tighter proxy, but bodyweight works as a starting approximation for most people)
• Fat: 25–35% of total calories
• Carbohydrate: remainder of calories after protein and fat are accounted for

Calorie targets vary widely by person. A rough orienting range: 1,600–2,000 kcal/day is common for an adult woman in a modest deficit; 2,000–2,600 kcal/day for maintenance at moderate activity; adjust from there. These are not prescriptions.

1.2 Distribute targets across meal slots

Map the daily target to the actual meal slots the person is eating. A common and effective default is unequal distribution that front-loads protein:

• Breakfast: ~20–25% of daily calories; at minimum, anchor to a protein source
• Lunch: ~30–35% of daily calories; typically the leftover-heavy slot
• Dinner: ~35–40% of daily calories; the primary cooking event of the day
• Snack(s) if any: the remaining calorie budget

For Macro-Tracked mode: assign gram targets to each slot, not just calorie percentages. Fat is the easiest macro to exceed accidentally — oils, nut butters, dressings, cheese, and avocado all carry significant fat that is easy to under-count. Pre-committing fat sources per meal slot catches this drift before it happens.

1.3 Identify the constraint tier

Before touching recipes, rank the dietary constraints in order of strictness:

• Hard constraints (allergies, intolerances, religious prohibitions): non-negotiable, zero-tolerance
• Strong preferences (one person is vegetarian but lives with meat-eaters): respected in full, drives the base layer
• Soft preferences (dislikes cilantro, prefers not to eat fish): accommodated where easy, can be routed around

In a multi-person household, the plan's base layer must satisfy all hard constraints and all strong preferences. Soft preferences are accommodated at the divergence point level (e.g., the cilantro is served on the side).

Phase 2 — Build the Component Inventory

This is the structural departure from the "seven separate dinners" approach. Instead of planning meals directly, plan components — proteins, carbohydrates, vegetables, and sauces that can be assembled in multiple combinations throughout the week.

2.1 Select 2–3 anchor proteins

These are the proteins that will be batch-cooked at the start of the week and recombine into different meals. Selection criteria:

• Versatile: can appear in at least 3 different meal formats (bowl, wrap, salad, stir-fry, soup)
• Economical: cost per gram of protein is reasonable
• Aligns with dietary constraints

Examples of strong anchor proteins: shredded chicken thighs (cheap, forgiving to cook, endlessly remixable), ground beef or turkey (fast, takes any seasoning), canned or dried legumes (plant-based anchor; also a carbohydrate source), hard-boiled eggs (fast prep, high protein density, inexpensive), tofu pressed and pre-baked (plant-based, absorbs marinades well)

2.2 Select 1–2 grain/carbohydrate bases

These carry the bulk of carbohydrate calories and provide the "bed" on which other components sit. They batch-cook well and hold for 4–5 days refrigerated. Good defaults: cooked white or brown rice, roasted sweet potato, cooked quinoa, pasta (cook day-of or day-before), roasted or boiled baby potatoes.

2.3 Select 3–5 vegetables

Aim for variety in color (which tracks micronutrient diversity), at least one raw option and one roasted option. Select by:

• What is in season (cheaper, fresher)
• What is already in the fridge and needs to be used (Waste-First mode: this drives the list, not the other way around)
• Versatility — broccoli works roasted, in stir-fry, in soup; spinach works in eggs, salads, pasta, curries

2.4 Select 2–3 sauces or flavor profiles

This is the underestimated lever. A single batch of chicken thighs can become completely different meals across the week — teriyaki bowl Monday, chicken tacos Tuesday, Mediterranean salad Thursday — driven entirely by the sauce and accompaniments. Plan sauces explicitly; make or buy 2–3 for the week. Keep calorie-dense sauces (tahini, peanut sauce, oil-heavy dressings) pre-portioned and tracked if in Macro-Tracked mode.

2.5 Map components to meal slots

Now create the week's plan by assigning component combinations to meal slots — not by writing recipes per day, but by noting which components are combined and which flavor profile applies:

Monday dinner: Anchor protein A + grain base 1 + vegetables 1 & 2 + sauce 1 (Asian)
               Tuesday dinner: Anchor protein A + grain base 2 + vegetables 3 + sauce 2 (Mexican)
               Wednesday dinner: Anchor protein B + grain base 1 + vegetables 4 & 5 + sauce 3 (Mediterranean)
               ...

This takes about 10 minutes once the component inventory is chosen. It is much faster than writing recipe names because the cooking decisions are already made at the component level.

Phase 3 — Design the Weekly Skeleton

The weekly skeleton assigns structure to the week so that energy-intensive cooking happens at high-energy times, and low-effort assembly happens on low-energy evenings.

3.1 Identify your prep window(s)

Most households have one or two viable prep windows per week. Common patterns:

• Sunday batch + Wednesday refresh: Sunday handles all protein batch-cooking, grain prep, and vegetable washing/chopping. Wednesday does a smaller refresh: cook a second protein if needed, replenish grains, rotate vegetables.
• Single-session Sunday: Works well when the week's component inventory is small (2 proteins, 1 grain, roasted vegetables) and everything holds 5+ days.
• Evening prep for next day: Better for households without a weekend prep window; 20 minutes of advance prep the night before instead of batch-cooking.

3.2 Apply a day-of-week logic layer

Assign meaning to each day based on reality, not idealism:

• Monday: High-motivation, fresh fridge. Use a slightly more involved assembly or a new component combination. Batch-cooked protein is freshest.
• Tuesday–Wednesday: Midweek. Reliable leftovers from Monday dinner should cover at least one lunch slot. Dinners should be 15-minute assemblies from the component inventory.
• Thursday: Often a low-energy evening. Pre-plan a "throw it in a pan" meal or designate this as the soup/stew night where something simmers hands-off.
• Friday: Use-it-up day. Deliberately plan Friday dinner to consume any component inventory that will not safely hold the weekend. Stir-fry, grain bowls, and fried rice are natural use-up formats.
• Saturday: If eating out or ordering once per week, Saturday is the natural choice — it consumes no prep.
• Sunday: Leftover lunch or eggs. The batch-cook prep window is here, not a cooking-from-scratch dinner.

3.3 Assign breakfast and lunch slots

The strongest default for both meal categories: simplicity through repetition. Most people tolerate breakfast repetition without boredom (the same two options on rotation is common and effective). Lunches are naturally handled by the prior night's leftovers — plan for this deliberately rather than hoping it happens.

Breakfast rotation (pick 2):

• Option A: high-protein egg-based (scrambled eggs + vegetables, or a protein shake with fruit)
• Option B: grain-based (oatmeal with protein powder stirred in, or Greek yogurt parfait)

Assign Option A to some days, Option B to others. That is the entire breakfast system.

Lunch system:

• Default: previous night's dinner leftovers
• Backup (no leftovers): pre-made components assembled in 5 minutes (protein + grain + vegetable + sauce from the inventory)
• True backup (nothing available): eggs, canned sardines, or a simple sandwich — keep these ingredients permanently stocked

Phase 4 — Build the Grocery List

4.1 Derive quantities from the plan, not from instinct

Walk through every meal slot in the skeleton. For each:

• Identify every ingredient needed
• Note the quantity required for that meal slot
• Add it to a running ingredient list

Do this mechanically. Many people over-buy by adding "a bit extra just in case" at every step, which compounds into significant over-purchase. Commit to buying exactly what the plan requires, plus one small buffer (see 4.3).

4.2 Collapse ingredient overlap

This is where the component-inventory approach pays off at the shopping stage. Because multiple meals share the same anchor proteins, grains, and vegetables, the grocery list is dramatically shorter than a seven-separate-recipes list would be.

Go through the raw ingredient list and consolidate:

• 400g chicken thighs (Monday dinner) + 300g chicken thighs (Wednesday dinner) = 700g chicken thighs total, one purchase
• 1 head broccoli (Tuesday stir-fry) + broccoli for Wednesday lunch box = 1.5 heads broccoli, one purchase
• Baby spinach for Thursday salad + spinach for Saturday eggs = one 150g bag

Collapsing overlap also catches cases where two recipes call for the same pantry item (olive oil, garlic, canned tomatoes) so you buy it once.

4.3 Add the pantry-gap buffer, not an open-ended top-up

Check the pantry staple inventory collected in the context-loading gate. Add only what is actually missing or nearly gone. Do not add "I should probably stock up on X" items to this week's budget list — that is pantry restocking, which is a separate exercise.

4.4 Organize by store section

Group the collapsed list by store department: produce, meat/fish, dairy, canned/dry goods, frozen, refrigerated non-dairy, bakery/bread. This prevents backtracking through the store and reduces impulse purchases from unstructured browsing.

4.5 Estimate total cost before shopping

Do a rough per-item estimate. If it exceeds the budget, look for substitutions at the protein level first (chicken thighs instead of salmon; dried beans instead of pre-cooked pouches; bone-in instead of boneless). Do not try to save budget by buying less of a vegetable and planning to supplement with something — that introduces a gap that generates waste later.

Phase 5 — Execute the Batch-Cook Session

5.1 Order of operations within the prep session

The goal is to run multiple cooking methods simultaneously so that a 2-hour session yields 5–6 days of components, not 2 hours of serial cooking.

Effective sequencing:

1. Start anything that takes the longest first (dried beans soaking → pressure cooker; whole grains into the rice cooker; pork shoulder or whole chicken into the oven)
2. While long-cook items run, chop and prep vegetables; marinate proteins that need 20+ minutes
3. Sheet-pan roast vegetables once the oven is free or at a different temperature rack
4. Stove-top items last: sauces (they are fast), hard-boiled eggs, any quick-sear proteins

5.2 Storage conventions

Label every container before it goes into the fridge with: contents + date made. Use this rule for safety:

• Cooked proteins: safe for 4 days refrigerated; freeze beyond that
• Cooked grains: safe for 5 days refrigerated
• Roasted vegetables: safe for 4 days refrigerated
• Raw chopped vegetables: varies — onion and bell pepper hold 5 days; leafy greens, 2–3 days max
• Sauces: store separately from the components they dress; combine at assembly time to prevent sogginess

5.3 Freeze strategically

If the plan does not use a component within its safe window, freeze it on day 2 or 3 — not the day before it would go bad. Freezing saves a component; waiting too long converts it to waste. Shredded chicken, cooked ground meat, cooked legumes, and most cooked grains freeze well. Raw marinated proteins freeze excellently and can be pulled for next week.

Phase 6 — Leftover and Remix Logic

Leftovers are not an accident — they are a resource that must be planned for explicitly.

6.1 Name every leftover slot in the plan

At the point of planning, designate specific meal slots as "leftover slots." Do not leave them as TBD. Example: Tuesday lunch = Monday dinner leftovers. Friday dinner = use-up stir-fry from remaining components. This prevents the situation where you cook a large batch but then also plan a different meal for the next day's lunch, and the leftover sits until it goes bad.

6.2 Remix rules: same ingredient, different form

The key to avoiding leftover fatigue is changing the format while reusing the ingredient. A three-step remix chain for any protein:

• Night 1 (primary form): Protein as the main, with grain and vegetable sides in their natural forms (e.g., roasted chicken thighs with rice and broccoli)
• Night 2 / Day 2 (deconstructed): Same protein shredded or sliced, served differently — as a taco filling, in a grain bowl with a different sauce, tossed with pasta and garlic oil
• Day 3 (incorporated): Protein chopped small, incorporated into something where it is one component among several — fried rice, soup, frittata, grain salad

This three-form approach means a single batch of protein can legitimately cover three distinct eating occasions without tasting like repetition.

6.3 Friday stir-fry / grain bowl rule

Friday should be explicitly named the "inventory clearance" dinner in the plan. Pull all remaining component inventory. If there are three vegetables left, a partial portion of two proteins, and leftover rice: that is fried rice night, or a grain bowl, or a quick soup. This single convention eliminates most end-of-week waste by design.

Phase 7 — Household Adaptation

7.1 The shared base layer principle

In a household with mixed dietary needs, identify the overlapping acceptable set: what can everyone eat without complaint or compromise? Build the base layer of every meal from this intersection. Then add divergence elements at assembly time, not at cooking time.

Example: one partner eats meat, one is vegetarian. The base layer is roasted vegetables, grain, and a shared sauce. The meat-eater adds shredded chicken at assembly; the vegetarian adds roasted chickpeas. One cooking session, two compliant plates.

7.2 Calorie scaling for different-size eaters

If the household has people with meaningfully different calorie needs (growing teenager vs. adult cutting weight, for example), scale portions at the plating step rather than making separate meals. Cook a larger batch of protein and grain. The higher-calorie eater takes a larger portion; the lower-calorie eater a smaller one. The grocery list scales up slightly but the cooking and system overhead do not.

7.3 Picky eaters and component flexibility

Picky eaters (especially children) are most easily managed by the component approach: serve components separately on the plate rather than as a mixed dish. A child who will not eat broccoli in a stir-fry will often eat plain roasted broccoli on the side. A child who will not eat the sauce eats the component unsauced. Build this flexibility into the plan explicitly — do not fight it.

7.4 Designated personal meals

Some households have one person who eats very differently (athletic meal prep, elimination diet, specific medical protocol). If that person's needs cannot be accommodated in the base layer without overcomplying the entire household, designate their meals as a parallel track: they batch-cook their specialized components separately, but share the grocery-list-building session to take advantage of shared pantry staples and reduce store trips.

Worked Example: 7-Day Plan for One Person, Moderate Macro Targets

Inputs:

• 1 adult, moderate activity, goal: maintain weight with adequate protein
• Approximate daily targets: 2,000 kcal / 150g protein / 55g fat / 200g carbohydrate (Quick-Start reasonable estimate — not personalized)
• No dietary restrictions
• Budget: $80/week
• Has: rice cooker, sheet pans, one cast-iron skillet
• Prep window: Sunday 1.5 hours

Component Inventory Selected:

Breakfast Rotation (both options prepped or purchased):

• Option A (M/W/F/Sun): 3 scrambled eggs + 1 cup spinach sautéed in pan → ~350 kcal / 27g protein
• Option B (T/Th/Sat): Greek yogurt (200g full-fat) + 30g rolled oats + 1 tbsp peanut butter → ~380 kcal / 22g protein

7-Day Meal Map:

Consolidated Grocery List:

Produce:

• Broccoli (1 large head)
• Bell peppers, red and yellow (3 total)
• Baby spinach (150g bag)
• Cherry tomatoes (250g)
• Baby potatoes (500g)
• Lemon (2)
• Fresh ginger (small knob)

Protein:

• Boneless skinless chicken thighs (900g)
• Canned tuna in water (4 cans × 140g)
• Eggs (12-pack)
• Salmon fillet (1 portion, ~180g, bought midweek)

Dairy / refrigerated:

• Greek yogurt, full-fat (500g tub)

Dry / canned:

• White rice (1 kg bag — if not already stocked)
• Rolled oats (if not stocked)
• Peanut butter (if not stocked)

Condiments / pantry (check stock, buy only what's missing):

• Soy sauce, sesame oil, honey, Dijon mustard, olive oil, dried herbs (thyme or Italian blend)

Estimated total: $55–70 depending on store and regional pricing, well within the $80 budget.

Common Failure Modes

Planning aspirationally, not realistically The most common failure: planning 7 elaborate dinners when the household historically cooks 4. Start with 4 planned dinners + 1 leftover night + 1 eat-out night + 1 simple night (eggs, pantry soup). Add complexity only after the simpler plan runs successfully for 3+ weeks.

Underestimating fat and over-estimating protein from label-reading alone In Macro-Tracked mode, oils added to pans, butter on toast, and dressings used more generously than measured are the most common sources of calorie and fat overshoot. The fix: pre-measure or pre-portion fat sources at the start of the week rather than adding them to taste.

Batch-cooking at the wrong time Batch-cooking Sunday morning when the household needs to leave at noon creates a rushed, incomplete prep that covers 3 days, not 5. Survey the actual available window (not the ideal one) and size the batch accordingly.

Buying perishables without a use within 2 days Fresh fish, soft herbs, delicate greens, and ripe berries have short windows. If the plan uses fresh salmon on Saturday, buy it Thursday or Friday — not as part of Sunday's big shop. Route high-perishable items to a midweek top-up.

No designated "use it up" meal Skipping the Friday inventory-clearance dinner means leftover components pile up over the week and become a Friday fridge full of partial containers that feel like a burden rather than a resource. Name the Friday (or lowest-energy day) slot explicitly as the use-up meal before the week begins.

One household member's strict restriction silently overrides the plan In Household mode, failing to audit every planned component against every member's hard restrictions before shopping creates an embarrassing discovery at dinner time. Do the hard-constraint audit before the grocery list is built, not after.

Abandoning tracking because one day went over target In Macro-Tracked mode, a single day over-target is noise, not failure. The appropriate response is to note it, understand what caused the overshoot (usually underestimated fat), and apply that information to the following day or the next week's plan construction. Abandoning the tracking system because of one imperfect day is the most common path back to no system at all.

Output Format / Deliverable Spec

A complete plan produced by this skill consists of five documents or sections, which may be combined into a single structured artifact or separated as distinct files:

1. Nutritional Frame Summary

• Daily calorie target and macro targets in grams
• How targets are distributed across meal slots (breakfast / lunch / dinner / snack)
• Any notes on target source and adjustment schedule

2. Component Inventory Table

• Columns: Component type | Specific item | Quantity to batch-cook | Days it covers | Compatible meal formats
• Includes sauces and flavor profiles

3. Weekly Meal Map

• 7-column table (one column per day)
• Rows: Breakfast / Lunch / Dinner / Notes (leftover source, prep note, eating-out flag)
• Each cell identifies: components used + sauce/format — not a full recipe name

4. Consolidated Grocery List

• Organized by store section
• Quantities derived from the meal map with ingredient overlap collapsed
• Pantry-check items flagged separately (buy only if stocked below threshold)
• Cost estimate per section and total

5. Batch-Cook Session Plan

• Ordered by cooking method and time (longest-cook items first)
• Estimated total prep session duration
• Storage labels with safe-use-by dates per component
• Freeze candidates flagged if component will not be used within safe refrigeration window

Sources consulted in authoring this skill: macro-focused meal planning methodology drawn from published nutrition education resources including Lillie Eats and Tells (macro planning framework), Life with Less Mess (printable macro planning system), Project Meal Plan (waste-reduction strategies), Goldilocks Kitchen (batch cooking methodology), and general dietary guidance from Nutrition.gov and Mayo Clinic Press on food shopping and budget meal planning.

Quality checklist

Before returning the plan, check every item below and revise the plan where one fails.

• [ ] The plan matches the household's actual cooking capacity — complexity is added only after a simpler plan has run, not aspirationally
• [ ] In Macro-Tracked mode, added fats (pan oil, butter, dressings) are pre-measured in the plan, not left to taste
• [ ] The batch-cook session fits the household's real available window, and the batch is sized to what that window can produce
• [ ] High-perishable items are routed to a midweek top-up rather than the big shop when their use falls late in the week
• [ ] A use-it-up meal is named on an explicit day before the week begins
• [ ] In Household mode, every planned component was audited against every member's hard restrictions before the grocery list was built
• [ ] All five deliverables are present: nutritional frame, component inventory, weekly meal map, consolidated grocery list with pantry-check flags, and the batch-cook session plan with storage dates
• [ ] Grocery quantities derive from the meal map with overlaps collapsed, and freeze candidates are flagged where refrigeration windows are exceeded

Related skills

• grocery-list-for-goals — Turns a set macro target into a shoppable list, prioritizing what must be bought precisely over what can flex with the budget.
• sustainable-diet-selection — Matches a diet pattern to a trainee's cooking bandwidth, social exposure, and rule tolerance so it survives past the first few weeks.
• meal-prep-system-selector — Matches a meal-prep system to real kitchen skill, schedule volatility, and flavor fatigue instead of the default batch-cook template.