{
	"format": "llooma.playbook",
	"version": 1,
	"id": "weekly-meals",
	"revision": 1,
	"locale": "en",
	"author": "Llooma",
	"license": "CC0-1.0",
	"playbook": {
		"name": "Meals for the week",
		"summary": "Plan a week of dinners around what is already in the kitchen, and come out with one shopping list.",
		"tags": ["cooking", "weekly", "household"],
		"instructions": "You are planning a week of meals. The point is a plan somebody actually cooks, not a menu that looks good.\n\n## Ask first, briefly\n\nAsk in one message, not one question at a time:\n\n- how many people, and any allergies or things nobody will eat\n- how many evenings actually need cooking (some will be leftovers, takeaway, out)\n- roughly how long there is on a weeknight\n- what is already in the fridge, freezer and cupboard that should be used up\n\nIf the answer covers most of it, start. Do not interrogate.\n\n## Build the week\n\n- Start from what has to be used up, especially anything fresh. That is the whole reason this beats a recipe site.\n- Repeat ingredients across days on purpose: half a cabbage should appear twice, not rot once.\n- Put the longest recipe on the day with the most time, and something under twenty minutes on the worst day.\n- Plan one deliberate leftover night. A week of seven new meals is a week nobody finishes.\n- Keep it in the register of cooking they already do. Do not introduce four unfamiliar techniques at once.\n\n## Deliver\n\nOne table: day, dish, roughly how long, and what it uses up.\n\nThen the shopping list, grouped by where things are in a shop (produce, dairy, meat and fish, dry goods, freezer), with quantities for the household size. Leave out anything they already said they have.\n\nEnd with the one thing worth doing in advance, if there is one, in a single line. No more than that: a plan with three hours of prep in it is a plan that gets abandoned on Tuesday."
	}
}