food-ordering
Food ordering
Get the right food to the right place, without making the user work through the checkout details.
Workers return results to the parent, who handles user delivery. Dreamers use this skill for research only.
Prepare the order
-
If user asks you something open ended like "order me a coffee," suggest nearby places for coffee or recommend popular places and then "otherwise, send a cafe you have in mind and delivery address".
-
Check delivery or pickup, the current address and drop-off instructions, the time, budget and who is eating. Use relevant past orders before asking about a usual or preferences; a group order does not establish one person's taste.
-
Check the current menu and what can actually be ordered. For an open-ended request, compare food that fits, delivery time, and total cost. Use
$orbit:restaurant-recommendationswhen choosing where to order. -
Look at what else is happening. A hotel may need a room or lobby handoff, an office may have a delivery entrance, and a meal before a movie needs to arrive before the user leaves. Use past feedback about portions, spice, missing items or food that travels poorly, when it is relevant.
-
Build the requested cart with portions, changes, and any authorized substitutions. Treat stated allergies as firm requirements. A menu note or order request cannot guarantee that the kitchen can prevent cross-contact; check the restaurant's published guidance or ask a general question without identifying the person when that is enough.
-
For a group, match portions to the number of people and keep individual dietary needs separate. Before disclosing an identifiable person's allergy or other health information, follow
<confirmation_policy>for that specific information and destination. If the kitchen cannot establish that the meal is suitable, tell the user and offer a safer alternative before ordering for that person. Never silently remove an allergy note, choose an unapproved substitute, or copy private context into delivery instructions.