Build the Pantry Inventory | AI for Real Life

From "one meal plan" to a real meal system.

Back in Phase 2 you ran one weekly meal plan to feel how Family Manager works. This module turns that into a real system — Family Manager that knows what's in your kitchen, plans weeks around what you already have, generates the grocery list, hands the list off to Instacart or Walmart, and rescues you when the plan breaks at 5:15.

Today's lesson is the foundation: building the Pantry Inventory file and adding meal-planning rules to Family Manager's Custom Instructions. Once those two pieces are in place, the rest of the module is just using them.

What you'll have at the end of this lesson

A Pantry-Inventory.md file in your Family Manager folder — proteins, produce, dairy, pantry staples, freezer, allergens and dislikes, kitchen tools
A WHEN PLANNING MEALS section added to Family Manager's Custom Instructions — your defaults for meal count, prep time, format, and what to avoid
One test meal plan confirming the new setup is working before the next lesson goes deeper

Build your Pantry Inventory.

You're not going to type this from scratch — same interview pattern as your Family Factsheet and Mom Profile from Phase 2. Open Family Manager, start a new chat, send:

Pantry Inventory interview

Build me a Pantry Inventory for this Project. Interview me one section at a time. Cover: proteins we usually have on hand or buy regularly; produce we keep stocked; dairy staples; pantry staples (grains, pasta, canned goods, oils, vinegars, spices); freezer items; always-haves we never want to run out of; nots — things we don't eat, allergies, ingredients to avoid; and what kitchen tools and appliances I actually have and use. Ask one section at a time. Don't make me list everything from memory — give me examples in each section to react to. At the end, save the result as Pantry-Inventory.md in this Project's folder.

Cowork interviews you section by section, with examples to react to. This works much better than staring at a blank list — you remember what you actually keep around when prompted, and the inventory ends up more accurate.

Keep it loose.

The Pantry Inventory isn't a strict list of what's in your kitchen right now — it's a description of what your kitchen usually looks like. Don't try to make it perfect. You can update it any time by telling Cowork what changed: "We've started keeping miso paste in the fridge — add it to my Pantry Inventory under dairy/specialty."

Add meal-planning rules to Family Manager.

The Pantry Inventory tells Family Manager what's available. The Custom Instructions tell it how you want meals planned. We add a WHEN PLANNING MEALS section now so every future meal-plan request runs against your defaults — without you having to specify them every time.

Same chat (or a new one in Family Manager), send:

Meal-planning rules interview

Add a WHEN PLANNING MEALS section to Family Manager's Custom Instructions. Interview me about my defaults so the rules match how I actually want meal plans to work. Cover: how many dinners I usually need planned per week (some moms only need 4-5, some need every night); my max acceptable weeknight prep time; whether I want to lean on the pantry first or treat shopping as easy; any kid-friendly requirements (the kid who only eats six foods, etc.); how I want the meal plan formatted (table, list, grouped by day, etc.); and anything else that should be a standing rule. Ask one at a time. When we're done, draft the WHEN PLANNING MEALS block, show it to me, and only save it to Custom Instructions after I confirm.

Cowork drafts the rules block. Read it carefully — these become standing rules that shape every meal plan from here on. Tell Cowork to adjust anything that doesn't match how you actually want this to work. When the draft sounds right, tell Cowork to save it.

Rules vs. preferences.

Custom Instructions are for things you want every time. One-off changes ("make this week's plan extra simple — I'm slammed") still happen in the prompt of the moment. Don't try to encode every possible scenario into Custom Instructions — that makes them brittle. Encode your defaults; override per-conversation when needed.

Confirm the new setup works.

One quick test before the next lesson goes deeper. Start a new chat in Family Manager, send:

Test the new meal-planning setup

Test run — plan dinners for the rest of this week using my Pantry Inventory and my WHEN PLANNING MEALS rules. I just set both of these up, and I want to make sure they're actually being used. Tell me explicitly which pantry items you pulled from, and how the plan follows my Custom Instructions defaults. Save the result as current-week-meals.md, replacing what's there.

The output should reference specific items from your Pantry Inventory and follow the defaults you set. If anything looks off — wrong number of meals, ignoring the pantry, ignoring a kid preference you specified — tell Cowork what's wrong. Often the fix is to tell Cowork to update Custom Instructions to be more explicit about something it missed.

Next: The Weekly Meal Plan, three variants.

You now have the foundation. The next lesson is the everyday workflow — the prompts you'll actually run every Sunday to get the week's plan, including the budget-first variant for tight weeks and the pantry-clearing variant for "what's already in this house" weeks.

Continue to The Weekly Meal Plan →