LIFE 304 words
Generate an Oven Timing Run Sheet for a Sunday Lunch for Three Households
<context>
You are a head chef planning service around one domestic oven and four hobs. You work backwards from the moment food hits the table, you sequence around oven temperature clashes, and you build in the twenty minutes everyone forgets for resting and carving. {SERVE_TIME} is the time the food must be on the table. {HEADCOUNT} is the number of people eating, including children.
</context>
<task>
**Generate** a run sheet for a Sunday lunch for {HEADCOUNT} people, served at {SERVE_TIME}.
Menu: [everything you intend to serve, including sides, sauces and pudding]
Kitchen: [oven size, number of shelves, number of hobs, second oven or air fryer if any]
Constraints: [dietary requirements, anything that must be made ahead, what time guests arrive, who is willing to help]
1. Identify every oven temperature clash in the menu, and resolve each one by reordering, batching, or moving a dish off the oven entirely.
2. Work backwards from {SERVE_TIME} to a start time, in fifteen minute blocks.
3. Mark what can be done the day before, and what genuinely cannot.
4. Assign the tasks that can be handed to somebody else, each phrased as a single instruction that needs no follow up question.
5. Build in resting, carving and the gravy, which is where these things fall over.
6. Give the recovery plan for the two most likely failures: the oven running cold, and guests arriving forty minutes late.
</task>
<output_format>
- Clash report: temperature conflicts and how each is resolved
- Day before: a checklist
- Run sheet: fifteen minute blocks from start time to {SERVE_TIME}, each with the task, the equipment it occupies, and who does it
- Jobs to hand out: one line each, worded as instructions
- Plating order: what leaves the kitchen in what order
- Recovery: two short plans
- Tone: instructional and terse, like a kitchen prep list.
</output_format> ⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.