Start with the week you will actually have
Mark which meals you need to plan before asking for recipes. A late arrival, an evening out and a quiet afternoon with time to cook are different starting points. Tell the assistant which nights need very little preparation and where a flexible meal would be more useful than another ambitious recipe.
Decide the result you want: a few dinner ideas, a complete menu or a checked shopping list. Include how many people you are planning for, the equipment available and ingredients you prefer to use. Avoid giving a product access to calendars or shopping accounts when a short summary is enough for this first plan.
Check what is already there
Seattle Public Utilities recommends looking through the kitchen before planning and building a shopping list around the meals you expect to eat. Apply that idea to the information you give the assistant: write down a small inventory you checked, rather than asking it to assume what is in your fridge.
Distinguish a known quantity from a guess. “One unopened packet” and “possibly some left” should lead to different shopping-list entries. Ask the assistant to keep uncertain items on a check-before-buying list. A photograph or a chat description cannot establish every ingredient, condition or quantity.
Reference: Seattle Public Utilities: meal planning and buying what you need
Give it a practical brief
The invented example below is a planning exercise, not a tested menu, a nutrition prescription or a report of an order placed by Twin. Replace its details with your actual needs. For any ingredient restriction that matters, check the original recipe and product information yourself rather than relying on an AI summary.
Ask for a small first version. It is easier to correct three meals than an elaborate month of recipes. If the assistant proposes too much work, change the constraint clearly: one pan, fewer new ingredients or a shorter active-preparation time. Keep your other preferences in the revised plan.
Reconcile the shopping list against the recipes
Ask the assistant to combine repeated ingredients without losing their units. Then compare the list with each recipe and your checked pantry inventory. A spoonful, a packet and a weight are not interchangeable quantities. Keep an unresolved conversion visible until you can verify it.
Check actual pack sizes, availability and the total in your chosen shop before buying. Prices and quantities in a generated plan can be assumptions. If a substitution is needed, inspect how it changes the recipe and your own ingredient requirements. A saved list is prepared work; a cart and a confirmed order are later stages.
Where Twin fits
The Twin team publishes this original workflow to make everyday delegation more concrete. It describes a plan you can inspect, correct and use with a service you already have. It does not promise a particular saving, a healthy outcome or an automatic grocery order.
Twin’s customer operator and optional app are in development. The early-access invitation reaches the team; it does not collect a pantry inventory, connect shopping accounts or authorize a purchase. If planning still takes too much effort, simplify the brief before adding more connections.