Playbooks · Everyday tasks · last verified 2026-10-23

Plan a week's meals and a grocery list with a chatbot

For a busy parent × planning seven dinners and one grocery list × with ChatGPT, in plain chat — no file upload needed.

Before you start

You need a ChatGPT account and, before you type anything, four facts written down: how many people you cook for, any allergies or foods to avoid, how many nights you can actually cook (versus leftovers or takeout), and what is already in your fridge, freezer, and pantry. The plan is only as useful as those constraints — a chatbot cannot see your kitchen.

Time and cost: NOT_MEASURED. No price or time claim is made here, because shopping costs and cooking times depend on your store and household.

Do not paste children's names, medical details, or anything beyond the food constraints the plan needs. "Nut allergy" is enough; a diagnosis is not.

What "done" looks like

At the end of one sitting you have a seven-day dinner list, a grocery list grouped by store section, and a short list of leftovers or pantry items the plan reuses. You have not bought anything yet — the list is the result, and shopping is a separate step.

Steps

1. Give the constraints first. Paste a prompt like this, filled in with your own facts:

   Plan 7 dinners for 2 adults and 2 children. One adult has a nut allergy.
   We can cook on Monday, Tuesday, Thursday, and Sunday. Wednesday and
   Friday are leftover nights, and Saturday is takeout. We already have
   rice, pasta, canned tomatoes, and chicken stock. Keep weeknight meals
   to one pot or one pan where possible, and reuse one cooked protein
   across two nights.

2. Ask for the plan as a table. Follow up with:

   Put that in a table with one row per day: day, meal, main protein,
   and what it reuses from an earlier night. Flag any meal that needs
   more than 30 minutes of hands-on cooking.

   Asking for the table makes gaps visible: a night with no plan, or a protein that appears once and never again, stands out.

3. Turn the plan into a grocery list, then split it. Paste:

   Now make a grocery list for exactly these 7 meals. Group it by
   store section (produce, meat, dairy, pantry, frozen). Leave out
   everything I already have: rice, pasta, canned tomatoes, chicken
   stock. Put quantities next to every item, and mark any item that
   is only used in one meal.

4. Fix the plan before you fix the list. Read the table first. If a meal will not work — an ingredient nobody eats, a cooking night you do not have — say so in plain words ("Swap Thursday's meal: no fish on Thursdays") and ask for a revised table. Only ask for a revised grocery list after the meals are settled, or the list will keep drifting out of sync with the plan.
5. Copy the final list out of the chat. Paste it into your notes app or print it. The chat is a draft; the list you carry into the store is the working copy, and you will cross items off it by hand.

Check the agent's work

• Every allergy or food to avoid you named is absent from every meal — search the plan for the ingredient, do not skim it.
• Every cooking night matches a night you said you can cook, and leftover nights actually point at an earlier meal.
• Every grocery item has a quantity, and no item on the list duplicates something you said you already have.
• Any single-use item is a deliberate choice, not an accident — a spice or sauce bought for one meal should be one you want to keep using.
• Nothing on the list is a quantity you cannot buy (for example, a fraction of an egg or a cut of meat in an odd weight) — adjust those before shopping.

What can go wrong

• The plan ignores a constraint. Chatbots drop constraints when the prompt gets long. If an allergy ingredient appears, restate the constraint alone and ask for a corrected plan.
• Portions are vague. "Serves 4" means different things for toddlers and teenagers. State ages or appetites in step 1 if quantities keep coming out wrong.
• The list and the plan disagree. This happens when you edit meals after the list is made. Re-ask for the list from the final table, rather than patching it by hand.
• It invents a dish that does not fit your kitchen. A meal needing equipment you do not own is a prompt problem: name your equipment limit ("no slow cooker, no grill") in the first prompt.

Limits

• The chatbot does not know your store's prices, stock, or layout, and this playbook makes no claim about either. Check prices and availability at your store before you rely on the list.
• Nutrition and allergy safety are your check, not the chatbot's. If a meal's safety matters, verify its ingredients against the product labels you buy.
• No step here requires a file upload or a web search, and none is claimed. If you want current prices, that is a separate check you do yourself at the store or on the store's site.

Verification

Checked 2026-10-23. This page was not run end to end; its capability claims rest on provider documentation fetched this run. Sources: ChatGPT as a conversational assistant you type requests to and refine with follow-ups is the ordinary chat interaction described in OpenAI's research and file pages below; no file-upload, browsing, or pricing capability is claimed on this page, so no further capability needs grounding. Sources consulted: OpenAI — Research with ChatGPT (chat, follow-up questions, reviewing cited sources); OpenAI Help Center — Uploading files and audio to ChatGPT (not used by this playbook's steps; listed so the reader can see what was checked and set aside). Limits of this verification: provider pages describe what the product can do, not whether a given week's plan will suit your household — that check is the "Check the agent's work" section above.

Back to: Everyday playbooks hub · Skills index