A weekly meal plan works when three things survive contact with real life: the plan itself, the recipes behind it, and one grocery list that covers the lot. ChatGPT or Claude can draft all three in minutes — and with Thoughts connected, each part lands on your iPhone where the week actually happens. This guide walks through a complete Sunday planning session: the brief that produces a realistic plan, how to save plan, recipes and list as separate thoughts, and how to reuse last week's plan instead of starting from a blank chat every time.
Set up once
Keep a synced Recipes project in Thoughts and connect your assistant with MCP (ChatGPT steps · Claude steps). If you already save individual recipes using the recipe workflow, you are set up — meal planning is the same shelf, used at week scale.
One optional thought pays for itself immediately: “How we eat”. Two or three lines your assistant can reread every week — household size, dietary rules, the slow cooker you actually use, Tuesday's twenty-minute limit, foods nobody will eat twice. Save it once in Recipes, then start each planning session with “read my How we eat thought first”.
Brief like a person, not a catering company
Meal plans fail on ambition, not imagination. A brief that respects your calendar produces a plan you will still be following on Thursday:
Plan dinners for Monday to Friday for two adults. Monday and Thursday must be 25 minutes or less. One vegetarian night, one fish night, nothing with mushrooms. Reuse ingredients across nights where sensible, and leave Friday flexible — suggest something that works with whatever is left. Use my How we eat thought in Recipes for the ground rules.
Ask for the plan first, alone, in a compact day-by-day format. Read it as a week, not as five independent dinners: Is anything perishable scheduled too late? Are two heavy cooking nights back to back? Swap days in the chat until the week feels like your week. Only then ask for recipes:
Now write each dinner as a standalone recipe: title, servings, time, ingredients with quantities, numbered steps. Keep weeknight ones genuinely simple.
Save three things, separately
1. The plan
Save the week plan as a thought in Recipes titled “Week of 20 Oct — dinners”.
The plan thought is your week's map: what is for dinner, which nights are quick, what Friday's fallback is. Date in the title, because you will want this again in a month.
2. The recipes worth keeping
Save the stir-fry and the salmon recipes as their own thoughts in Recipes. Skip the pasta bake — I have my own version.
Not every planned dinner deserves a permanent page. Save the new and the good; let the filler nights live only inside the plan thought. Your cookbook stays curated, which matters for browsing later — see organising saved recipes so you cook them again.
3. One grocery list
Build one grocery list for the whole plan: quantities added up, grouped by shop section, excluding the staples in my How we eat thought. Flag anything I should buy midweek instead. Save it as “Shop: week of 20 Oct”.
The list mechanics — merging, pack sizes, shopping from the phone — are covered fully in grocery lists from ChatGPT to Thoughts.
During the week: the plan bends, the notes keep up
Thursday's fish becomes Friday's because Thursday ran late. Edit the plan thought in Thoughts — two taps — rather than reopening a chat. Cooked something and loved it? Add a line to its recipe thought while the pan is still warm: “needed 5 more minutes; double the sauce”. Those marginal notes are what turn generated recipes into your recipes, and they are exactly what your assistant will read next time it plans around that dish.
Next week: start from what worked
Read my “Week of 20 Oct — dinners” thought and my How we eat thought. Plan next week in the same style, repeat the salmon, drop anything similar to the pasta bake, and keep the same time rules.
This is where saving plans pays compound interest. The assistant is no longer inventing a generic week for a generic household; it is iterating on your recorded weeks, your constraints, your annotated recipes. Because ChatGPT and Claude share the same Thoughts library, whichever you open on Sunday can run the ritual.
Keep it sustainable
Plan five dinners, not seven — leftovers and life fill the rest. Repeat favourites shamelessly; novelty is the assistant's bias, not your family's. And review quantities before you shop: generated plans occasionally over-cater vegetables and under-cater the thing everyone fights over. A two-minute read of the list beats a second trip.
Fifteen minutes on Sunday, three thoughts saved, zero “what's for dinner?” all week. That is the entire system.
Frequently asked questions
How do I save a ChatGPT meal plan into Thoughts?
With Thoughts connected, ask the assistant to save three separate thoughts in your synced Recipes project: the dated week plan, each keeper recipe on its own, and one consolidated grocery list. Each is then on your iPhone for the week.
What makes a meal-plan prompt realistic?
State household size, per-night time limits, dietary rules, equipment you actually use and nights that must be flexible. Saving a short How we eat thought in Thoughts lets the assistant reread your ground rules every week.
Should I save every recipe in the plan?
No. Save the plan itself, then save only the new or especially good recipes as standalone thoughts. Filler dinners can live inside the plan thought so your cookbook stays curated.
Can next week's plan learn from this week's?
Yes. Ask the assistant to read last week's saved plan thought and your recipe notes, then plan in the same style, repeating what worked and dropping what did not. Both ChatGPT and Claude can do this from the same library.