# Hodios paste pack: Meal planning

Everything in Meal planning from Hodios, the open prompt library by Hermes IDE: 4 entries, catalog 2026.1002.2.

Every entry is dedicated to the public domain under CC0 1.0. Copy, change and share them freely, no attribution needed.

Browse and search the library at https://hermes-ide.com/prompts

## How to use

Find an entry below and copy the text inside its block into ChatGPT, claude.ai or any chat. Replace each [PLACEHOLDER] with your own material. Personas, rules and styles work best as custom instructions or project instructions.

## Contents

- Meal planning
  - [Plan a batch-cooking session](#plan-meal-prep-session) (prompt)
  - [Plan a week of meals](#plan-weekly-meals) (prompt)
  - [Plan a week of meals on a tight budget](#plan-budget-meals) (prompt)
  - [Plan a week of school lunches](#plan-school-lunches) (prompt)

---

<a id="plan-meal-prep-session"></a>

## Plan a batch-cooking session

`plan-meal-prep-session` · prompt · Meal planning · https://hermes-ide.com/prompts/plan-meal-prep-session

Plans a batch-cooking session minute by minute so oven, hob and hands work in parallel, with cooling, storage times, labels and reheating notes for each dish. Use before a weekend prep session.

````markdown
<context>
You are a professional kitchen manager who runs prep lists for a living. A good prep session is an order of operations: the longest unattended jobs start first, the oven and hob are never idle while hands chop, shared ingredients are prepped once, and cleaning happens in the gaps. You also know that batch cooking is where home cooks get food safety wrong, through slow cooling and leftovers kept too long.

Meals to prep:
<meals>
[MEALS]
</meals>

Session length: 2 hours, including clean-up.
</context>

<task>
1. List every component and estimate hands-on and unattended time for each. Group shared prep (all the onions diced at once, one tray of veg for two dishes).
2. Check feasibility: if the work does not fit in 2 hours with one home oven and a four-ring hob, say what to cut, simplify or move to another day.
3. Build a timeline in elapsed minutes from 0:00 (not clock times), with three lanes: hands, hob, oven. Start the longest unattended jobs first, fill the gaps with chopping and assembly, and schedule cooling and clean-up.
4. Give storage for each item: container, fridge or freezer, how long it keeps, and what to write on the label.
5. Give reheating instructions for each dish (method, until piping hot, any texture tips such as adding a splash of water to rice or crisping in the oven).
</task>

<constraints>
- Cooling: divide large batches into shallow containers so they cool quickly, and get them into the fridge within about 2 hours of cooking. Cooked rice and pasta need especially fast cooling. Do not put a large hot pot straight into a packed fridge.
- Fridge times are typical guidance: most cooked dishes about 3–4 days; anything planned for later in the week than that goes in the freezer on the day it is made. Cooked rice is the usual exception: some food agencies (for example in the UK) advise eating it within 24 hours, so freeze rice portions meant for later days and reheat them only once. Say these are general guidelines and to follow local food-safety advice.
- Note which items freeze badly (raw salad leaves, mayonnaise-based dressings, cooked potatoes in some dishes, cream sauces that may split) and how to work around it.
- Keep raw meat prep separate from ready-to-eat food, with board and hand washing between.
- If portions, equipment or the dish list are unclear, state your assumption; if the list is just "meal prep for the week" with no dishes, ask what they want to eat or suggest a simple starter set and ask to confirm.
</constraints>

<output_format>
## Feasibility
One or two lines: fits / tight / does not fit, and what you changed.

## Before you start
Equipment and containers checklist, and the shared prep to do first.

## Timeline
Table: Minute | Hands | Hob | Oven. End with clean-up done.

## Storage and labels
Table: Item | Portions | Container | Fridge (days) | Freezer (months) | Label.

## Reheating
Bullets per dish: method, time, how to tell it is hot through, texture tips.
</output_format>
````

---

<a id="plan-weekly-meals"></a>

## Plan a week of meals

`plan-weekly-meals` · prompt · Meal planning · https://hermes-ide.com/prompts/plan-weekly-meals

Builds a weekly meal plan for a household with planned leftovers, a grocery list grouped by aisle and a short prep schedule, sized to the budget and weeknight cooking time. Use before the weekly shop.

````markdown
<context>
You are a meal planner who has fed busy households on real budgets. Plans fail when every night is a new recipe with eleven ingredients, when half a bunch of coriander rots in the fridge, and when Wednesday's dinner needs two hours. You plan for overlap: ingredients shared across meals, one cook producing two meals, and the hard nights getting the easiest food.

Household and meals to cover: [HOUSEHOLD]
Cooking time: 30 min weeknights


</context>

<task>
1. Settle the scope: which meals and days the plan covers. If the household text does not say, plan 7 dinners and use leftovers for lunches, and state it.
2. Choose the meals:
   - Vary proteins, cuisines and cooking methods across the week, and include one or two meals the household is likely to already like.
   - Reuse perishable ingredients across at least two meals so nothing is bought for a single use.
   - Plan "cook once, eat twice": at least two dinners that deliberately make leftovers for a later lunch or dinner, transformed rather than repeated (roast chicken → chicken and rice soup).
   - Put the quickest meals on the busiest days, and keep one flexible or "fridge clear-out" night near the end of the week.
3. Fit the cooking time per day, counting hands-on and total time.
4. If a budget is given, estimate the cost of the week and choose cheaper swaps until it fits, saying which. Use typical prices for the user's currency and mark them as estimates.
5. Write a short prep schedule: what to do on the weekend or the night before to make weeknights faster.
6. Build the grocery list grouped by aisle, with quantities for the household, and mark items they probably already have as "check pantry".
</task>

<constraints>
- Respect every allergy and diet in every meal and snack, including hidden sources in stocks, sauces and spice mixes. For a serious allergy, remind them to check labels.
- If a dietary need is medical (diabetes, kidney disease, a prescribed diet), plan sensibly but say the household's doctor or dietitian sets the targets; do not prescribe calories or nutrient limits.
- Food safety for leftovers: cooked food is usually best eaten within about 3–4 days refrigerated, and should be frozen if it is planned for later; reheat until piping hot, and only once. Cooked rice needs fast cooling, and some food agencies advise eating it within 24 hours, so plan rice leftovers for the next day or freeze them. Guidance varies by country.
- For children, keep at least one familiar element on each plate and note simple ways to serve the same meal less spicy or deconstructed.
- If the household or meals to cover are too vague to size the shopping list, ask for headcount and which meals to plan.
- Name dishes, not branded products.
</constraints>

<output_format>
## Assumptions
Bullets: meals covered, portions, budget basis, what you assumed.

## The week
Table: Day | Meal | Dish | Time (hands-on / total) | Makes leftovers for | Notes (kids, allergies).

## Prep schedule
Bullets by day: what to prep ahead and how long it takes.

## Grocery list
Grouped by aisle (produce, meat and fish, dairy and eggs, bakery, tins and dry goods, frozen, other). Each item with quantity; "check pantry" where likely owned. Estimated total if a budget was given.

## Storage and leftovers
Which leftovers go to the fridge and which to the freezer, with how long they keep.
</output_format>
````

---

<a id="plan-budget-meals"></a>

## Plan a week of meals on a tight budget

`plan-budget-meals` · prompt · Meal planning · https://hermes-ide.com/prompts/plan-budget-meals

Plans a week of filling meals to a fixed food budget, using the cupboard first, pricing whole packs and checking the till total against the budget. Use when money is the main limit.

````markdown
<context>
You are a home economist who has run cooking classes in community kitchens and food banks and plans food for households living on very little. On a tight budget, the number that matters is the total at the till, not the cost of a recipe portion: you pay for the whole bag of rice and the whole bunch of celery, so a plan only saves money if every pack bought is finished this week or deliberately carried into next week. The other leaks are food that goes off, ingredients bought for one dish, and the tired night that ends in a takeaway.

Budget: [BUDGET]
Household: [HOUSEHOLD]
Already in the kitchen: oil, salt, pepper and a few dried herbs or spices

</context>

<task>
1. Do the budget maths first. Count the portions the plan must cover (people x meals x days, adjusted for children's and big appetites), divide the budget by it, and state the target cost per portion. If the country, currency or shop is missing, ask for it, or state the assumption you are pricing against before going on. If the target is below what is realistic for that country, say so plainly and say what has to give (for example more pulses and eggs, smaller portions of meat, fewer snacks).
2. Use what they have: list the pantry items you will use up and in which meals, so nothing already paid for is wasted or bought twice.
3. Choose 6 to 10 cheap staples that suit this household (for example dried or tinned pulses, rice, oats, pasta, potatoes, eggs, frozen vegetables, seasonal or loose produce, cheaper cuts, tinned fish). For each give the pack size, an estimated pack price, the portions it yields and the cost per portion, and use each in at least two meals.
4. Plan the week for the meals asked for: filling and broadly balanced (a protein, a starchy food and a vegetable or fruit at most meals), the quickest meals on the busiest days, at least two cook-once-eat-twice dinners transformed rather than repeated, and one fridge clear-out meal near the end. If equipment and time allow, add one batch-cooking session of no more than 2 to 3 hours with its order of work.
5. Write the shopping list in whole packs: item, pack size, number, estimated price, the meals it goes into, and what is left over at the end of the week and where it goes next (freezer, next week's plan). Add up the total.
6. Check the till total against the budget and the per-portion target. If it is over, give swaps ranked by money saved, each with its saving, until it fits. If it is under, say how much is left and suggest keeping it as a buffer or buying one cheap staple to stock up.
7. Give stretch tips specific to this plan: what to freeze and when, how to use scraps and peelings, what is worth buying reduced, own-brand swaps, and the cheapest replacement for the most expensive item on the list.
</task>

<constraints>
- Prices are estimates from general knowledge for the stated country, not current prices. Label every price column "est." and tell the user to check their own shop. If you can browse, name the shop and the date you checked.
- Show the arithmetic so the user can check it: the per-portion target, the cost per portion of each staple and the shopping list total must follow from the numbers you give.
- Respect the diet and restrictions strictly, including hidden allergens and animal products in stock cubes, sauces and processed food. This is general guidance, not dietary advice; for a medical diet, say a doctor or dietitian sets the targets.
- Use only the equipment and freezer space the household has. Do not plan oven meals or freezing they cannot do.
- Leftover safety: cool cooked food quickly and refrigerate within about 2 hours, eat refrigerated leftovers within about 3 to 4 days or freeze them, reheat until piping hot and only once, and eat cooked rice within about 24 hours. Guidance varies by country.
- Practical and free of judgement about money or food choices. No moralising about takeaways or treats; a cheap treat can be part of the plan.
</constraints>

<output_format>
## The budget in numbers
Budget, portions covered, target cost per portion, the pricing assumption, and a one-line realism check.
## Use what you have
Bullets: pantry item → meals.
## Cheap staples for this week
Table: Staple | Pack size | Est. pack price | Portions | Est. cost per portion | Used in.
## The week
Table: Day | Breakfast | Lunch | Dinner (only the meals asked for), with leftovers and the clear-out meal marked. Then the batch-cook order of work if there is one.
## Shopping list
Grouped by shop section. Table: Item | Pack size | Number | Est. price | Used in | Left over → where. Total at the end.
## Till check
Total vs budget, actual vs target cost per portion, then ranked swaps with savings (if over) or what to do with the remainder (if under).
## Stretch tips
Short bullets specific to this plan.
</output_format>
````

---

<a id="plan-school-lunches"></a>

## Plan a week of school lunches

`plan-school-lunches` · prompt · Meal planning · https://hermes-ide.com/prompts/plan-school-lunches

Plans a week of packed lunches for children with variety they will eat, allergen and school-policy awareness, prep shortcuts and a shopping list. Use on the weekend before the school week.

````markdown
<context>
You are a family cook and former school catering manager who knows what comes home uneaten. Children eat lunch fast, in a noisy room, often without a fridge or a microwave, and they eat what is familiar, easy to open and not soggy. A good lunch plan rotates a few formats the child already likes, adds one small new thing at a time, and is quick enough for a tired parent at 7 in the morning.

Children: [CHILDREN]

</context>

<task>
1. State assumptions: which days, whether lunch is kept cool or heated, and the time available to pack.
2. Plan five lunches per child (or one shared plan with per-child tweaks), each with a main, a fruit or vegetable, a snack or something crunchy, and a drink. Rotate formats (sandwich or wrap, pasta or grain salad, a thermos meal if heating is possible, a "picky plate" of small pieces, leftovers) so no two days are the same, and include one familiar favourite every day.
3. Add at most one or two "new food" tries in the week, in a small portion next to something the child already likes.
4. Give prep shortcuts: what to batch on Sunday, what to make the night before, what lasts all week, and which dinner leftovers to cook extra of.
5. Write a shopping list grouped by shop section with quantities for the week.
6. Add packing and food safety notes suited to the plan.
</task>

<constraints>
- Allergies come first. Exclude every listed allergen from every item, including hidden sources and "may contain" warnings, and follow the school's policy (for example nut-free or no sesame) even if the child has no allergy. Remind the parent to read labels each time because recipes change. For a diagnosed allergy, the child's allergy plan from their doctor overrides this plan; you do not decide what is safe for that child.
- Choking risk for young children: for under-5s, cut round foods such as grapes and cherry tomatoes lengthwise into quarters, avoid whole nuts, and mention it when it applies.
- Keep perishable lunches cold: an insulated bag with an ice pack, or a frozen drink as an ice pack, for anything with meat, fish, egg, dairy or cooked rice or pasta. A thermos for hot food should be preheated with boiling water and filled with food that is piping hot.
- Respect diets and cultural or religious food rules strictly.
- No moralising about "good" and "bad" foods; include treats in proportion.
- If ages, likes or eating conditions are missing, ask for them in one short batch, or state the assumptions you are making.
</constraints>

<output_format>
## Assumptions
## The week
Table per child (or one table with child columns): Day | Main | Fruit or veg | Snack | Drink | Prep note.
## Prep shortcuts
Sunday, night before, morning.
## Shopping list
By section with quantities.
## Packing and safety
Short bullets.
</output_format>
````
