When should you use it?
- You cook most nights for a household
- Weekly planning eats your Sunday
- Your store offers online pickup or delivery
Not for: Strict medical diets without a dietitian; Stores whose terms forbid automated ordering
What do you need, and what do you get?
You need
- Household likes and dislikes
- Feedback on recent meals
- Pantry list
- Store account
You get
- Two-week plan for approval
- Shopping list doc
- Filled cart awaiting payment
- Kitchen screen with tonight's recipe
How does it work, step by step?
- Collect feedbackAfter each cycle, note which meals were hits and misses.
- Draft the planHave the assistant propose two weeks of meals using that feedback and send it for review.
- Build the listAfter approval, write the shopping list plus low pantry staples into a dated doc.
- Fill the cartA browser agent adds the list to your store cart and stops at checkout.
- Confirm and displayYou review and pay; the kitchen screen shows the recipe and when to thaw proteins.
The prompt
Our own prompt, inspired by u/WeezerHunter on r/ClaudeAI and written to work in Claude and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Plan {days} days of dinners for {household}. Likes: {likes}. Avoid: {avoid}. Feedback from last cycle: {feedback}. Return the plan for my approval first. After I approve, write a shopping list grouped by store section, plus staples from this pantry list that are low: {pantry}. For each dinner, note any protein that must be thawed and when.
Inspired by u/WeezerHunter on r/ClaudeAI: AI is a HelloFresh killer. Automated meal prep and grocery ordering workflow.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Substitutions and out-of-stock items need a rule, or the agent picks oddly.
- Pantry counts drift; do a quick real check before each order.
Our take
Two things make this more than another meal-plan prompt. The feedback loop from last cycle's meals means the plan improves instead of repeating, and the handoff through a plain doc keeps the planning model and the shopping step loosely coupled. u/WeezerHunter's loop starts with feedback: after each cycle, note which dinners were hits and misses, so the next two weeks build on them rather than repeating. The plan waits for approval before any list is written, which keeps the household in charge of what gets eaten. Writing the list into a dated plain document is a quiet strength, because any shopper, human or tool, can work from it. Set rules for substitutions and out-of-stock items, or the agent will pick oddly. Pantry counts drift, so do a real check before each order. The browser agent stops at checkout and a person pays. Strict medical diets need a dietitian, and stores that forbid automated ordering should be shopped by hand.
Where the time goes back: Planning, list writing and cart filling run on their own; you approve the menu and tap pay.
FAQ
Does the agent pay?
Why a shared doc between agents?
Source and credit
Inspired by u/WeezerHunter on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- AI is a HelloFresh killer. Automated meal prep and grocery ordering workflow.
- Creator
- u/WeezerHunter on r/ClaudeAI
- Published on
- Original date
- Oct 4, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.