Michael Fenech's exact prompt designs a three-agent team on your Chief of Staff bot: a Meal Organiser plans easy meals for your diet, a Shopper fills your online grocery cart (you do the final payment), and a Cooking agent gives step-by-step instructions. It maps the pipeline for your review first.
4 steps. Do them in order.
Copy it. Change the names. Keep the job.
You are a systems architect specializing in multi-agent AI workflows, tasked with designing a team of three specialized agents that together eliminate the time I spend planning, ordering, and cooking food. My situation: I'm [YOUR CONTEXT / TIME CONSTRAINT]. I shop for groceries online at [GROCERY SITE] and want a small agent team to handle the entire process from meal planning through to cooking instructions, with the only manual step being final payment. Design the following three agents, each with a clear role definition, scope, and handoff logic: 1. Meal Organiser Agent Invoked on-demand when I specify how many days I need meals for ([MEAL TYPES - DINNER, LUNCH etc], sometimes a single day). Generates meals strictly following a [DIET TYPE] diet. Every meal must be [COMPLEXITY STANDARD - EASY etc] to cook - this is a hard constraint, not a preference. Outputs a clear meal list with the specific food items and ingredients needed for each meal, structured so it can be handed directly to the Shopper Agent. 2. Shopper Agent Receives the finalized food items list from the Meal Organiser Agent. Its job is to translate that list into an actionable shopping task: matching each ingredient to what's needed for purchase on [GROCERY SITE] and preparing them to be added to my cart. Does not complete payment - that remains my manual final step. Should flag any ambiguities (quantity needed, brand preference, substitutions) rather than guessing silently. 3. Cooking Agent Draws from the meals already created by the Meal Organiser Agent. When I indicate I want to cook a specific meal, it provides a step-by-step cooking guide for that meal. Instructions must match the [COMPLEXITY STANDARD - EASY etc] set by the Meal Organiser Agent - no unnecessary complexity, no advanced techniques, minimal steps. For each agent, define: its exact scope of responsibility, what information it needs as input, what it hands off and to whom, how it should behave when information is missing or ambiguous (ask me directly rather than assuming), and how the three agents connect into one coherent pipeline (Meal Organiser -> Shopper Agent, and Meal Organiser -> Cooking Agent, both triggered by me on-demand). Do not build or execute anything yet. First, map out this three-agent system clearly - showing each agent's role, inputs, outputs, and handoffs - so I can review and confirm the design before we move to implementation.
via @michael_fenech_ · Tweet by @Michael_Fenech_
Same category. Different job.
Vox runs two real-money errands on one rule. A bargain tracker: exact specs, acceptable condition, max price - when a listing checks every box the bot buys or bids; over budget comes back as a link. And a haircut booked end to end, paid via Stripe Link. The rule: within range, go ahead; outside it, ask first.
Morgan Linton's idea for a bot no chatbot can be: photograph every appliance sticker, breaker panel, filter size and paint can once, and the bot files it all for years. A cheap monthly check flags expiring warranties and due filters - and when something breaks, one photo comes back as a one-page repair card.
Peter bought a $15 phone number on Bland, gave his Grok Bot the API key, and the bot worked out the rest. Now he asks it to call someone with instructions, it has the conversation and reports back - recording on request. It cloned his voice from a 10-second sample, and voicemails left on the number show up in the chat.
Robin Delta's beginner-to-pro Grok Bot guide: the install decisions that make a bot a worker not another chat window, a five-part task brief, the brief→observe→correct→schedule→deliver loop, and 21 bot builds worth stealing.