Weekly Dinner Planner

Output location and file contract

The primary output is a saved weekly bundle in the repo, not only an inline chat answer.

Create or update one folder per ISO week:

• weekly-plans/YYYY-Www/

Always create these files inside that folder:

1. veckoplan.md - overall weekly overview using templates/weekly-plan-output.md
2. inkopslista.md - detailed shopping list using templates/shopping-list-output.md
3. mandag.md
4. tisdag.md
5. onsdag.md
6. torsdag.md
7. fredag.md
8. lordag.md
9. sondag.md

Use ASCII file names for portability even though the content should stay Swedish.

If the prompt names a specific week, use that week. If the prompt says "nästa vecka", use the next ISO week relative to the current date. If the prompt is otherwise ambiguous, use the current ISO week and note the assumption in veckoplan.md.

When regenerating the same week, update the full bundle coherently so veckoplan.md, inkopslista.md, and the day files stay in sync.

Default household profile for this repo

If the user does not override these points, assume:

• no hard dietary restrictions
• mild, familiar flavors are safer for the children
• Swedish output is preferred
• weekday dinners should land around 45 minutes total
• budget should be considered, but there is no fixed spending cap
• preferences should be confirmed in conversation rather than read from a saved preferences file

If key information is missing, ask focused follow-up questions before finalizing the plan. The highest-value follow-ups are:

1. favorite family dinners to repeat or remix
2. specific dislikes or textures the children dislike
3. preferred shopping-list grouping if the user cares about it

Inventory handling rules

Read @inventory.csv before planning. Use references/inventory-schema.md as the parsing guide.

• Treat the CSV as the source of truth for what is already in the house.
• Keep Swedish item names and category context.
• Quantities are free-form and sometimes messy. Be conservative.
• Do not pretend to know exact servings from values like 200 g, 6st, or 100ml.
• If availability is uncertain, say so explicitly instead of assuming.
• When deciding what to buy, separate items into:
  • finns hemma
  • bör räcka
  • kontrollera hemma
  • behöver köpas

Meal-planning heuristics

Nutrition and calories

• Favor vegetables, legumes, beans, lentils, lean poultry, white fish, lighter dairy, and fiber-rich staples already in the inventory.
• Prefer leaner ingredient choices when calories can be lowered without making the meal feel punishing or less kid-friendly.
• Lean toward oven-baked, simmered, roasted, or stir-fried meals over deep-fried or very creamy options.
• Keep the meals nutrient-dense rather than simply small or restrictive.
• Give every dinner one explicit green side that suits the meal, choosing either a salad or a vegetable side.
• Report estimated kcal per portion, not fake precision.

Kid-friendliness

• Keep seasoning mild by default.
• Favor familiar formats such as pasta, rice bowls, tacos, mild curries, soups, oven trays, and simple fish or chicken dishes.
• Avoid stacking too many unfamiliar ingredients in the same dinner.
• If introducing something less familiar, pair it with a safe side or familiar starch.

Week structure

• Monday-Thursday: lower-friction dinners, about 45 minutes total, fewer pans, fewer fiddly steps.
• Friday-Sunday: still balanced, but allowed to be more festive, cozy, or slightly more elaborate.
• Reuse ingredients across nearby dinners to reduce cost and waste.
• Plan leftovers deliberately so dinner usually yields two lunch boxes for the next day.

Shopping-list behavior

• Base the shopping list on the chosen dinners, not on generic pantry replenishment.
• Default to grouping the shopping list by store section unless the user requests another format.
• Prefer overlapping ingredients across recipes when it keeps the week cheaper and simpler.
• Include ingredients for the green sides in the same planning pass, and reuse produce across multiple dinners when practical.
• Mark uncertain gaps clearly when the inventory quantity is ambiguous.
• Avoid buying specialty ingredients for only one small use unless they add clear value.

Suggested default groupings:

• Produce
• Dairy and eggs
• Meat and fish
• Pantry and dry goods
• Frozen
• Sauces, spices, and condiments

Daily recipe behavior

Each day file must be a practical home-cook recipe, not only a meal idea.

• Write the recipe in Swedish.
• Keep the steps easy to follow, concrete, and sequential.
• Say what comes from the inventory versus what must be bought.
• Include approximate amounts that fit the planned household portions.
• Include one explicit green side section for each dinner, choosing either a salad or vegetables.
• Note where the dinner should intentionally produce two lunch boxes.
• Avoid chef shorthand or vague instructions like "cook until done" when a clearer cue can be given.

Workflow

1. Read @inventory.csv.
2. Confirm or collect any missing planning constraints.
3. Resolve the target ISO week and output folder under weekly-plans/YYYY-Www/.
4. Identify inventory items that should be used soon or can anchor multiple meals.
5. Build a 7-day dinner plan that respects weekday/weekend effort, kid-friendliness, lighter calories, leaner ingredient choices, leftover goals, and one green side per dinner.
6. Estimate kcal per portion for each dinner and say when the estimate is rough.
7. Create veckoplan.md using the structure in templates/weekly-plan-output.md.
8. Create inkopslista.md using the structure in templates/shopping-list-output.md.
9. Create each day file using the structure in templates/daily-recipe-output.md.
10. Reply briefly in chat with the folder path and what files were written.

Output contract

Respond in Swedish by default.

Always create the repo files above, and ensure the bundle contains:

1. Antaganden - only when anything important is inferred or uncertain
2. Veckomeny - seven dinners, Monday through Sunday
3. Estimated kcal per portion for each dinner
4. Grönt till varje middag - one explicit salad or vegetable side for each dinner
5. Portioner/restlådor - note how the plan covers two lunch boxes
6. Inköpslista - both a summary inside veckoplan.md and a detailed actionable version in inkopslista.md
7. Smart att använda ur lagret - ingredients the plan intentionally uses from inventory
8. Ekonomi och återbruk - a short note on how ingredient overlap keeps costs down
9. Detaljerade dagsrecept - one recipe file per day

Output quality rules

• Be explicit when something depends on an uncertain inventory amount.
• Do not claim a full recipe pantry check if the CSV does not support that certainty.
• Prefer practical weeknight meals over aspirational ones.
• Keep kcal estimates believable and clearly approximate.
• Make the green side concrete and visible in the output instead of implying it in a serving note.
• Do not optimize calories so aggressively that the meals stop being satisfying for a family dinner.
• Keep the daily recipe files genuinely easy to cook from without having to reconstruct missing steps.

Example prompts

• Planera nästa veckas middagar utifrån @inventory.csv. Håll det barnvänligt, ganska lätt, och spara allt som veckofiler i repot.
• Gör en veckomeny måndag-söndag baserat på @inventory.csv. Vardagar max 45 minuter, helgen får vara lite festligare, och skapa receptfil per dag.
• Använd lagret i @inventory.csv och skapa en veckomapp med veckoplan, inköpslista och sju detaljerade middagsrecept.

Final checklist

• Inventory used first
• Target ISO week resolved
• weekly-plans/YYYY-Www/ created or updated
• veckoplan.md written
• inkopslista.md written
• mandag.md through sondag.md written
• Monday-Thursday kept simpler
• Friday-Sunday allowed more flair
• Leaner ingredients preferred where reasonable
• Estimated kcal per portion included for every dinner
• One explicit green side included for every dinner
• Shopping list only covers missing or uncertain items
• Leftovers considered for two lunch boxes