Turn the Contents of Your Fridge Into a Week of Dinners With an AI Assistant

Most meal-planning apps start with what you should buy. This walkthrough starts with what you already own. Half a bag of spinach, three eggs, rice, a lonely chicken thigh pack: an AI assistant is surprisingly good at turning that pile into a plan, as long as you give it the right inputs and check the right things afterward. Here's the whole process, start to finish.

Step 1: Take inventory in plain language

You don't need a photo or a spreadsheet. Type a messy list, quantities included where you know them: "6 eggs, 1 pack chicken thighs (about 500g), 2 cups cooked rice, half a bag of spinach, 1 onion, canned chickpeas, pasta, soy sauce, olive oil, a jar of salsa." Add your pantry staples in one line so the assistant doesn't suggest buying salt.

Then add the constraints that actually shape a week: how many people you're feeding, how many nights you want to cook (maybe four, with leftovers covering the rest), your time limit on weeknights, and any dietary rules. Be specific about allergies and hard "no" foods. Those aren't preferences; they're requirements.

Step 2: Use a prompt that asks for a plan, not a recipe dump

Here's a sample you can copy and adapt:

Here's what's in my kitchen: [your list]. Plan dinners for 4 nights for 2 people, each under 30 minutes. Use up the spinach and chicken first. Avoid peanuts and shellfish completely. For each dinner, give a one-line description and the key steps, not a full essay. Then give me a short grocery list of only what's missing, grouped by store section, with quantities.

Two details matter here. "Use up X first" tells the assistant what to prioritize, which is how you reduce waste. And asking for only what's missing keeps the grocery list from quietly doubling.

Step 3: Review it like an editor

This is the step people skip, and it's where assistants make their quiet mistakes. Run through four checks:

Allergens and restrictions. Read every ingredient, including sauces and stock. An assistant can follow "no peanuts" and still suggest a store-bought sauce that contains them. Treat its output as a draft, and check labels yourself when an allergy is involved.

Quantities. Assistants are decent at scaling recipes but not flawless. Sanity-check the grocery list against what each recipe needs, especially for things you buy by the package.

Food safety. If the plan leaves cooked chicken or rice sitting for days, ask the assistant when each dish should be eaten by, then confirm against your local food safety guidance. Don't rely on the model alone for this.

Reality. Does a "20-minute" dinner include chopping three vegetables? Ask it to flag which steps you can prep ahead on Sunday.

Step 4: Iterate once, then stop

Your first plan will probably have one dinner you don't want. Say so directly: "Swap Thursday for something with chickpeas, no oven." Assistants handle targeted edits well and handle vague dissatisfaction poorly. One or two rounds is plenty.

A good final move is asking for a consolidated version: the four dinners, a prep list, and the grocery list in one tidy block you can paste into your notes app or send to a partner.

A note on privacy and limits

You're sharing little more than a grocery list, which is about as low-stakes as AI use gets. But if you add health conditions to get tailored advice, remember you're handing over sensitive information, and an assistant is not a dietitian. For medical dietary needs, use the plan as a starting point and confirm it with a professional.

The takeaway: the winning pattern is simple. Give the assistant real inventory and clear constraints, ask for a short plan plus only the missing groceries, then spend your attention on the checks it can't do for you. Try it tonight with whatever is in your fridge, and see how many dinners you can get before you need a store trip.