Coordinate Meal Planning, Grocery Carting, and Cooking

Premise

Meal automation works as a handoff: one role plans within dietary rules, another builds the cart, and a third guides preparation from approved choices.

Setup

1. Record dietary rules, dislikes, household size, budget, and difficulty.
2. Connect the grocery site without unattended checkout.
3. Review the role design and test one day first.

Boundaries

• Allergies and medical diets are hard constraints.
• Unknown substitutions and quantities return for review.
• The human checks out and pays.

The planner proposes meals and outputs ingredients, quantities, pantry assumptions, and a consolidated list. The shopper maps the approved list to store products, flags unavailable items and substitutions, and prepares—but never buys—the cart. The cooking guide gives timed steps from the approved meal and purchased ingredients.

Define inputs, outputs, checks, and handoffs. No role may relax dietary rules or guess an allergy, substitution, quantity, or required brand.

Wait for approval of the design, plan, substitutions, and cart. Checkout remains mine.

Design a three-role food workflow using [DIET], [ALLERGIES], [PEOPLE], [BUDGET], [COOKING LIMIT], and [STORE]. Show the architecture before running it.