nutrition-and-meal-planning

$npx mdskill add Tibsfox/gsd-skill-creator/nutrition-and-meal-planning

Plan weekly meals balancing nutrition, budget, and food safety.

  • Builds a weekly menu respecting household constraints and preferences.
  • Uses plate method, macronutrient balance, and rotation heuristics.
  • Decides based on pantry, budget, prep time, and eater needs.
  • Outputs a structured weekly plan with leftover architecture and safety rules.

SKILL.md

.github/skills/nutrition-and-meal-planningView on GitHub ↗
---
name: nutrition-and-meal-planning
description: Household-scale nutrition planning that treats meals as a weekly system, not a series of independent decisions. Covers macronutrient balance, the plate method, weekly rotation, leftover architecture, pantry-to-plate translation, and the food-safety floor that every meal plan must meet. Use when building a weekly menu, adapting a diet to a new household member, planning for a week of predictable meals on a budget, or teaching a learner how a kitchen feeds people over time.
type: skill
category: home-economics
status: stable
origin: tibsfox
modified: false
first_seen: 2026-04-12
first_path: examples/skills/home-economics/nutrition-and-meal-planning/SKILL.md
superseded_by: null
---
# Nutrition and Meal Planning

Meal planning is a weekly system, not a nightly improvisation. The household has a finite set of eaters, a finite budget, a finite prep time window, a finite set of appliances, and a finite pantry. A good weekly plan respects all five constraints and still produces meals that are nutritious, varied, and safe. This skill catalogs the tools for assembling such a plan: the plate method, macronutrient balance, rotation and repeat heuristics, leftover architecture, pantry-to-plate translation, and the food-safety floor that no plan may violate.

**Agent affinity:** waters (seasonal and whole-food framing), child (technique-driven substitution), fisher-he (food-writing lens on what a meal should feel like)

**Concept IDs:** home-nutrition-basics, home-meal-rotation, home-food-safety

## 1. The Plate Method

The plate method is a shorthand that replaces calorie counting with a geometric target. On a nine-inch dinner plate:

- **One-half** of the plate is vegetables (two different colors, at least one non-starchy)
- **One-quarter** is a protein source (meat, fish, legume, egg, dairy protein)
- **One-quarter** is a starch (whole grain, potato, winter squash, bread)
- **A small portion** (roughly a tablespoon) of fat (oil, butter, nuts, dressing)
- **A fruit** or dairy serving on the side

The plate method is not a precise nutritional prescription. It is a visual heuristic that approximates the balance of a calorically adequate, fiber-rich, protein-sufficient meal for a non-athletic adult. It fails for specific medical diets (diabetes, kidney disease, celiac) and for very active or growing bodies, but it produces sound defaults for general household planning.

## 2. Macronutrient Balance

A household-scale plan should hit approximate daily targets for each eater:

| Macronutrient | Share of calories | Per kg body weight (adult) | Notes |
|---|---|---|---|
| Protein | 10-35% | 0.8-1.2 g/kg | Higher end for active or older adults; includes animal and plant protein |
| Fat | 20-35% | 1 g/kg | Prioritize unsaturated; saturated under 10% of calories |
| Carbohydrate | 45-65% | 3-5 g/kg | Prioritize whole grains, legumes, fruit, vegetables |
| Fiber | — | 14 g per 1000 kcal | Fiber counts toward carbohydrate; target 25-38 g/day for adults |

These are ranges, not floors. A household can be within range on every meal and still produce a diet that is monotonous or socially unpleasant. Range compliance is necessary, not sufficient.

## 3. The Weekly Rotation

A plan is a rotation, not a list. Over seven days, aim for:

- **Two to three protein sources** rotated across the week (e.g., chicken, fish, beans, eggs)
- **At least five different vegetables**, with repetition allowed across meals
- **Two to three starch types** (rice, bread, potato, pasta, beans as starch)
- **One "anchor meal"** that the cook can make from memory when the plan breaks
- **One "experiment meal"** that tries a new recipe
- **One planned leftover day** where the main dish is intentionally cooked in a double batch

The anchor meal is the single most important slot in the week. It is the meal the cook makes when tired, when the plan has already failed twice, when the store was out of the ingredient — a meal with short ingredient list, short cook time, and known-good outcome. Every household should be able to name theirs.

## 4. Leftover Architecture

Leftovers are not scraps. They are the second phase of a planned meal. Leftover architecture means designing meals so the remainder is a different dish the next day, not the same dish reheated. The discipline is:

- **Day 1 main** is the designed meal (roast chicken with vegetables)
- **Day 2 variant** uses the remainder in a different form (chicken soup from the carcass and leftover meat)
- **Day 3 rescue** is a last-use pattern (chicken-and-bean tacos, or a fried rice)
- **Trim to compost or freezer** by the end of day 3

This reduces food waste, spreads the labor of a long-cook meal across multiple days, and gives the cook variety without daily shopping. The architecture is pre-planned; if the cook waits until day 2 to decide what to do with leftovers, the leftovers typically rot.

## 5. Pantry-to-Plate Translation

A pantry is a latent meal plan. The discipline of pantry-to-plate translation is asking "given what is in the pantry, the freezer, and the fridge right now, what three meals can I assemble without shopping?" This is the anti-dote to the common failure mode where the cook has food but feels like there is nothing to eat.

The method:

1. **Inventory the proteins.** What protein is available: canned beans, eggs, frozen meat, leftover chicken, tuna?
2. **Inventory the starches.** Rice, pasta, bread, potatoes, oats?
3. **Inventory the alliums and aromatics.** Onion, garlic, ginger? These are the universal base for most savory dishes.
4. **Inventory the acid.** Lemon, vinegar, tomato, yogurt — something to brighten the dish.
5. **Match them.** Bean + rice + onion + tomato = beans and rice. Egg + pasta + garlic + lemon = pasta carbonara-ish. Chicken + potato + onion + vinegar = a roasted tray.

Most cuisines have a small number of core templates that can be re-expressed from whatever the pantry holds. Teaching the templates rather than the specific recipes is the high-leverage pedagogical move.

## 6. Food-Safety Floor

No meal plan is acceptable if it does not meet the food-safety floor. These rules are not negotiable.

| Rule | Specification | Why |
|---|---|---|
| Cold chain | Keep cold food at or below 4 C (40 F) | Below this, most pathogenic bacteria multiply slowly |
| Hot chain | Keep hot food at or above 60 C (140 F) | Above this, most pathogens cannot multiply |
| Danger zone limit | No more than 2 hours between 4 C and 60 C | Above 2 hours, bacterial load may reach unsafe levels |
| Cook temperatures | Poultry 74 C, ground meat 71 C, whole cuts of pork/beef 63 C with 3 min rest, fish 63 C, eggs until yolk firm | Kills common pathogens |
| Cross-contamination | Separate cutting boards or sequential use with hot soapy wash between raw meat and ready-to-eat food | Prevents transfer of raw-meat pathogens to salad and bread |
| Fridge hygiene | Raw meat on bottom shelf, covered, to prevent drip onto ready-to-eat food | Prevents contamination from leaks |
| Handwashing | 20 seconds of soap and water before food prep, after handling raw meat, after bathroom | First line of defense |

These rules apply regardless of how good the menu is. A beautifully designed week of meals with a cold-chain violation is not food, it is a risk event.

## 7. Dietary Adaptation

Households are rarely uniform. Adaptation is the skill of keeping the core plan while flexing around:

- **Allergies** (tree nut, peanut, dairy, egg, gluten, shellfish, soy, wheat, sesame — the big nine)
- **Medical diets** (diabetes, hypertension, kidney, celiac, phenylketonuria)
- **Religious constraints** (kosher, halal, Hindu vegetarian, Jain, Buddhist)
- **Ethical constraints** (vegetarian, vegan, flexitarian)
- **Texture needs** (infants, elderly, post-surgical)

The discipline is to design the plan around the most-constrained eater, then add unrestricted variants for others. A household with a celiac member uses gluten-free grain as the base; the rest of the household can still have bread as a side if they like. Designing around the least-constrained eater and then excluding the constrained eater is the common failure mode that produces social exclusion at the table.

## 8. Budget Discipline

A meal plan costs what it costs. The budget discipline is:

1. **Set a weekly total.** Explicit numeric budget for food.
2. **Reserve a floor for staples.** Rice, beans, pasta, flour, oil, eggs, seasonal vegetables — the base of the plan, bought in bulk.
3. **Allocate a flex.** A percentage (often 20-30%) for fresh produce, protein, and dairy that varies weekly with store specials and seasonal availability.
4. **Allocate an experiment.** A small slice (5-10%) for trying new ingredients — the learning budget of the household.
5. **Track actuals for one month.** Real spending vs plan. Adjust allocations until the plan is stable.

A plan that exceeds the budget is a failed plan no matter how nutritious it is. Treating the budget as a hard constraint forces the cook to find the nutritious meals that also fit.

## 9. Common Failure Patterns

| Pattern | Cause | Fix |
|---|---|---|
| "I planned all week and still ordered takeout twice" | No anchor meal; plan had no fallback | Name the anchor and keep its ingredients always stocked |
| "We waste so much produce" | Plan did not sequence perishables | Sequence fragile items (leaf greens, berries) early in the week |
| "Everyone is tired of this meal" | Rotation too narrow | Add one experiment meal per week, retire meals no one finishes |
| "The plan collapsed on day 3" | No buffer for unexpected evenings | Hold one freezer meal in reserve for collapse nights |
| "I can't afford this plan" | Overweighted toward expensive proteins | Shift toward legume-anchored meals 2-3 times a week |
| "The kids won't eat vegetables" | All-or-nothing serving | Introduce one new vegetable alongside a familiar one, repeat exposures |

## 10. Cross-References

- **waters agent** — Seasonal and farm-to-table framing for ingredient selection
- **child agent** — Technique-driven substitution when a recipe lacks an ingredient
- **fisher-he agent** — The experiential and social dimension of what a meal should feel like
- **food-technique-fundamentals skill** — The techniques that make the plan executable
- **household-economics-and-budgeting skill** — The budget frame within which the plan lives
- **household-systems-design skill** — The kitchen system that the plan depends on

## 11. References

- Dietary Guidelines for Americans, 2020-2025. U.S. Department of Agriculture and Department of Health and Human Services.
- Nestle, M. (2006). *What to Eat*. North Point Press.
- Pollan, M. (2008). *In Defense of Food*. Penguin.
- Food and Drug Administration. *Food Code* (current edition).
- Waters, A. (2007). *The Art of Simple Food*. Clarkson Potter.
- Child, J. (1961). *Mastering the Art of French Cooking, Vol. I*. Knopf.

More from Tibsfox/gsd-skill-creator

SkillDescription
3d-interaction-designDesign heuristics for three-dimensional interaction — input modalities (6DoF controllers, gaze, gesture, voice), selection and manipulation techniques (ray-cast, virtual hand, go-go, world-in-miniature), navigation (teleport, continuous, redirected walking), and feedback loops (haptic, audio, visual). Covers Fitts' law in 3D, discoverability vs affordance, safe-zone design, and comfort/simulator sickness mitigation. Use when designing VR/AR interactions, immersive walkthroughs, or any input system where the user's body is the controller.
accessibility-patternsProvides web accessibility best practices for semantic HTML, ARIA, keyboard navigation, color contrast, and screen reader patterns. Use when building UI components, reviewing accessibility, or when user mentions 'a11y', 'accessibility', 'ARIA', 'screen reader', 'keyboard navigation', 'WCAG'.
active-listeningActive listening techniques for effective communication. Covers attending behaviors, paraphrasing, reflective listening, clarifying questions, empathic response, barriers to listening, listening in conflict, and cross-cultural listening. Use when building listening skills, improving understanding in conversation, mediating disputes, or analyzing communication breakdowns.
adversarial-pr-reviewAdversarial spec-compliance PR review — cross-references diffs against approved specs, verifies runtime claims against source, detects competing PRs, audits scope/convention compliance. Use before merging.
agile-methodsAgile and Lean software development methodologies for iterative, adaptive project execution. Covers Scrum (roles, ceremonies, artifacts), Kanban (WIP limits, flow metrics), XP (TDD, pair programming, CI), SAFe overview, Lean Software Development (Poppendieck's 7 principles), user stories (INVEST criteria), estimation via story points and velocity, and the Agile Manifesto's values and principles. Includes Cynefin framework for methodology selection and GSD's relationship to Agile as a structured Lean variant.
algebraic-reasoningSymbolic manipulation, equation solving, and algebraic structures for mathematical reasoning. Covers distributive law, factoring, completing the square, linear through polynomial equation solving, systems of equations (substitution, elimination, Gaussian elimination, matrix methods), algebraic structures (groups, rings, fields), modular arithmetic, polynomial theory, and inequalities. Use when solving equations, simplifying expressions, working with algebraic structures, or performing symbolic manipulation.
algorithmic-awarenessUnderstanding how algorithmic systems shape what users see, know, and do -- from recommendation feeds to search ranking to credit scoring to hiring software. Covers the mechanics of recommendation systems, algorithmic bias and its sources, personalization's effects on information diets, opacity and accountability, AI limitations (hallucination, confident wrongness), and the human-in-the-loop question. Use when a learner needs to think critically about why particular content reached them.
algorithms-data-structuresAlgorithms and data structures from first principles through advanced analysis. Covers sorting (bubble, insertion, selection, merge, quick, heap, radix), searching (linear, binary, BFS, DFS, Dijkstra, A*), fundamental data structures (arrays, linked lists, stacks, queues, hash tables, trees, heaps, graphs, tries), complexity analysis (Big-O, Big-Omega, Big-Theta, amortized), recurrence relations, and algorithm design paradigms (divide-and-conquer, greedy, dynamic programming, backtracking). Use when analyzing, selecting, implementing, or comparing algorithms and data structures.
aminet-browserAminet search and browse: full-text search, category tree navigation, architecture filtering, package detail, and curated collections. Use when searching, browsing, or managing package collections.
aminet-emulatorFS-UAE emulator configuration and launch: hardware profiles, ROM management, WHDLoad integration, config generation, and state snapshots. Use when configuring emulation, managing ROMs, or launching Amiga software.