Meal Prep OS Skill
Meal prep fails two ways: the ambitious version (five new recipes, Sunday
dies, never again) and the boring version (one tray of chicken and rice
eaten with declining enthusiasm until Thursday's takeaway). The version
that survives is a system: cook components, not meals — two bases, two
proteins, two sauces — and recombine them so Wednesday tastes different
from Monday; start from what's already in the kitchen; keep Sunday under
90 minutes; and plan the Thursday dip on purpose, because the week's
weakest night is a design input, not a moral failure.
What This Skill Produces
- A Sunday cook plan, ordered for one oven and two burners, timed to
~90 minutes: what goes on first, what happens in the gaps
- The recombination map: components × 4–5 distinct meals (bowls,
wraps, salads, the fried-rice mercy move), so repetition isn't
repetitive
- The shopping delta: what to buy given what's already there — the
fridge inventory is the starting point, not the bin
- Storage & safety notes: what keeps how long, what freezes at the
start (the Thursday insurance), each day-count flagged as
general-guidance-verify-locally rather than gospel
- The Thursday plan: the deliberately-easiest meal or the blessed
freezer pull, scheduled in advance
Required Inputs
Ask for (if not already provided):
- What's actually there: fridge, freezer, cupboard staples (the honest
list, wilting herbs included)
- The week's real shape: how many lunches/dinners needed, who's eating,
which nights are hopeless
- Tastes and limits: dislikes, dietary rules, spice tolerance, the
"I'll never eat that as leftovers" list
- Equipment and time: oven/hob/airfryer/rice-cooker, and the honest
Sunday window
Framework
- Inventory before recipes. Everything gets a job or a verdict:
use-first (the wilting spinach anchors Monday), staple, or freeze-now.
The plan builds outward from what exists — this is where the takeaway
money is found.
- Components, not dishes. 2 bases (a grain, a roastable-starch) ·
2 proteins cooked plain-ish (seasoning at assembly, not in the batch —
the trick that keeps options open) · 2 sauces/dressings (the actual
flavor variety) · 1 crunchy thing. Six-ish components = the whole
cook.
- Order Sunday like a line cook. Oven items first (they're passive) →
grain on the hob → proteins while both run → sauces in the gaps →
cool properly before boxing (food-safety basics: cool fast, box
shallow, fridge within the safe window — flag exact hour/day numbers
as verify-with-local-guidance rather than asserting them).
- Map the recombinations explicitly. Monday bowl ≠ Wednesday wrap ≠
Friday fried-rice, from the same components. Write the map down —
variety that isn't scheduled doesn't happen; people eat the same bowl
until morale fails.
- Design the dip. The freezer portion made on Sunday IS the Thursday
plan. Naming it in advance converts the week's failure point into the
week's easiest win.
Output Format
## Fridge verdicts
[Use-first / staple / freeze-now — everything sentenced]
## Sunday, 90 minutes (one oven, two burners)
| Time | Doing | Waiting on |
## The components
[Bases · proteins (seasoned at assembly!) · sauces · crunch]
## The week's map
| Day | Meal | Built from | 2-min assembly note |
## Shopping delta
[Only what's missing, grouped by aisle]
## Storage & the Thursday plan
[What keeps/freezes (day-counts flagged as general guidance) · the
scheduled easy night]
Quality Checks
Anti-Patterns
Related
[[grocery-budget-audit]] finds the money this system saves;
[[weekly-review-ritual]] is where the 10-minute plan-next-week step lives;
[[bennett-time-audit]] for what the reclaimed weeknights become.
Example Trigger Phrases
- "What do I cook with what I have?"
- "We spend too much on takeaway."
- "I'm sick of eating the same thing four days."
1---2name: meal-prep-os3description: "Turn what's actually in the fridge and 90 minutes on Sunday into a week that mostly feeds itself — a cook-once-eat-thrice batch plan, the component method (bases, proteins, sauces that recombine so leftovers don't bore you), honest food-safety day-counts flagged, and the Thursday problem solved in advance. Use when someone says 'meal prep my week', 'what do I cook with what I have', 'we spend too much on takeaway', or 'I'm sick of eating the same thing four days'. Produces the Sunday cook plan, the recombination map, and the shopping delta."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/meal-prep-os7---89# Meal Prep OS Skill1011Meal prep fails two ways: the ambitious version (five new recipes, Sunday12dies, never again) and the boring version (one tray of chicken and rice13eaten with declining enthusiasm until Thursday's takeaway). The version14that survives is a *system*: cook components, not meals — two bases, two15proteins, two sauces — and recombine them so Wednesday tastes different16from Monday; start from what's already in the kitchen; keep Sunday under1790 minutes; and plan the Thursday dip on purpose, because the week's18weakest night is a design input, not a moral failure.1920## What This Skill Produces2122- A **Sunday cook plan**, ordered for one oven and two burners, timed to23 ~90 minutes: what goes on first, what happens in the gaps24- The **recombination map**: components × 4–5 distinct meals (bowls,25 wraps, salads, the fried-rice mercy move), so repetition isn't26 repetitive27- The **shopping delta**: what to buy given what's already there — the28 fridge inventory is the starting point, not the bin29- **Storage & safety notes**: what keeps how long, what freezes at the30 start (the Thursday insurance), each day-count flagged as31 general-guidance-verify-locally rather than gospel32- The **Thursday plan**: the deliberately-easiest meal or the blessed33 freezer pull, scheduled in advance3435## Required Inputs3637Ask for (if not already provided):38- What's actually there: fridge, freezer, cupboard staples (the honest39 list, wilting herbs included)40- The week's real shape: how many lunches/dinners needed, who's eating,41 which nights are hopeless42- Tastes and limits: dislikes, dietary rules, spice tolerance, the43 "I'll never eat that as leftovers" list44- Equipment and time: oven/hob/airfryer/rice-cooker, and the honest45 Sunday window4647## Framework48491. **Inventory before recipes.** Everything gets a job or a verdict:50 use-first (the wilting spinach anchors Monday), staple, or freeze-now.51 The plan builds outward from what exists — this is where the takeaway52 money is found.532. **Components, not dishes.** 2 bases (a grain, a roastable-starch) ·54 2 proteins cooked plain-ish (seasoning at assembly, not in the batch —55 the trick that keeps options open) · 2 sauces/dressings (the actual56 flavor variety) · 1 crunchy thing. Six-ish components = the whole57 cook.583. **Order Sunday like a line cook.** Oven items first (they're passive) →59 grain on the hob → proteins while both run → sauces in the gaps →60 cool properly before boxing (food-safety basics: cool fast, box61 shallow, fridge within the safe window — flag exact hour/day numbers62 as verify-with-local-guidance rather than asserting them).634. **Map the recombinations explicitly.** Monday bowl ≠ Wednesday wrap ≠64 Friday fried-rice, from the same components. Write the map down —65 variety that isn't scheduled doesn't happen; people eat the same bowl66 until morale fails.675. **Design the dip.** The freezer portion made on Sunday IS the Thursday68 plan. Naming it in advance converts the week's failure point into the69 week's easiest win.7071## Output Format7273```74## Fridge verdicts75[Use-first / staple / freeze-now — everything sentenced]7677## Sunday, 90 minutes (one oven, two burners)78| Time | Doing | Waiting on |7980## The components81[Bases · proteins (seasoned at assembly!) · sauces · crunch]8283## The week's map84| Day | Meal | Built from | 2-min assembly note |8586## Shopping delta87[Only what's missing, grouped by aisle]8889## Storage & the Thursday plan90[What keeps/freezes (day-counts flagged as general guidance) · the91scheduled easy night]92```9394## Quality Checks9596- [ ] The plan starts from the stated inventory — no recipe requiring a97 shop for its whole ingredient list98- [ ] Proteins are batch-cooked neutral with seasoning at assembly99- [ ] The Sunday timeline fits the stated window on the stated equipment100- [ ] Food-storage day-counts are flagged as general guidance, and101 anything genuinely risky (rice handling, reheating rules) points at102 official food-safety guidance rather than winging it103- [ ] The Thursday dip has a named plan, and at least one meal is104 structurally different from the others (not three bowls in a105 trenchcoat)106107## Anti-Patterns108109- [ ] Do not plan five distinct recipes — that's cooking all Sunday, and110 it's the version that dies111- [ ] Do not season the whole batch one way; flexibility lives at assembly112- [ ] Do not moralize about the takeaway habit — the system replaces it by113 being easier, not by shame114- [ ] Do not assert precise safety day-counts as fact — general guidance,115 flagged, with official sources for the risky items116- [ ] Do not ignore the "won't eat as leftovers" list — a plan the person117 won't eat is a compost schedule118119## Related120121[[grocery-budget-audit]] finds the money this system saves;122[[weekly-review-ritual]] is where the 10-minute plan-next-week step lives;123[[bennett-time-audit]] for what the reclaimed weeknights become.124125## Example Trigger Phrases126127- "What do I cook with what I have?"128- "We spend too much on takeaway."129- "I'm sick of eating the same thing four days."