Use when creating a restaurant menu, planning meals for a catering event, designing a weekly household menu, or developing a cycle menu for an institution
Scanned 9/8/2026
Install to Claude Code
npx -y skills add jeffreytse/grimoire-core --skill design-menu-planning --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Design Menu Planning?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeffreytse-design-menu-planning)More formats (shields.io, HTML) on the badges page.
---
name: design-menu-planning
description: Use when creating a restaurant menu, planning meals for a catering event, designing a weekly household menu, or developing a cycle menu for an institution
source: CIA "The Professional Chef" (9th ed.); Academy of Nutrition and Dietetics; National Restaurant Association Educational Foundation menu planning guidelines
tags: [cooking, menu-planning, nutrition, restaurant, food-service]
verified: true
---
# Design Menu Planning
Create a structured, balanced menu — for home, restaurant, or institution — that aligns nutritional goals, operational capacity, ingredient availability, and guest experience.
## Why This Is Best Practice
**Adopted by:** Culinary Institute of America (CIA), National Restaurant Association Educational Foundation, Academy of Nutrition and Dietetics, school nutrition programs (USDA NSLP), hospital food service, and all accredited food service management programs.
**Impact:** Restaurants with structured menu planning achieve 20-30% lower food cost than those without; school nutrition programs using cycle menus reduce food waste by ~35% (USDA FNS data); hospital menus designed by registered dietitians reduce patient length of stay by 0.5-1.2 days in studies measuring nutrition-sensitive outcomes; Cornell University research found menu structure and sequence influence caloric selection by 15-20%.
**Why best:** A menu is not a list of dishes — it is a system that determines purchasing, labor, equipment, food cost, nutritional adequacy, and guest satisfaction simultaneously. Planning it systematically ensures all these factors are balanced before service begins, not discovered through costly in-service failures.
Sources: CIA "The Professional Chef" 9th ed., Chapter 2; NRA Educational Foundation "MenuLogic" planning framework; AND Evidence Analysis Library, Menu Planning (2021); USDA NSLP Meal Pattern Requirements (2023).
## Steps
1. **Define the menu context and constraints** — Identify: audience (age, dietary restrictions, cultural context), service type (à la carte, fixed-price, buffet, institutional cycle), budget per person, equipment available, staff skill level, and any regulatory requirements (USDA school meal patterns, hospital therapeutic diet protocols).
2. **Establish nutritional parameters** — For institutional and healthcare menus: use USDA MyPlate or therapeutic diet standards (renal, diabetic, cardiac) as the framework. For restaurant menus: ensure the overall menu offers nutritionally diverse options even if individual dishes are indulgent. Document the target macronutrient and micronutrient goals per meal or day.
3. **Determine the menu structure** — Choose the organizational framework: traditional (appetizer/entrée/dessert), tasting menu (6-10 courses), cycle menu (rotating set over 4-6 weeks), prix fixe, or à la carte. The structure determines how many dishes are needed and how they relate to each other.
4. **Build the protein anchor for each meal** — For each meal position, select the protein anchor first. Proteins drive food cost, cooking method, and equipment use. Ensure variety across the week or menu: poultry, red meat, fish, legumes, eggs. No more than two meals in a row should share the same protein category.
5. **Pair grains, starches, and vegetables** — For each protein anchor, select complementary carbohydrate and vegetable pairings that: share no cooking equipment conflict, contrast in color and texture, and support the nutritional target. Classic pairings: lean protein + whole grain + bright vegetable; rich protein + acidic vegetable + neutral starch.
6. **Balance flavors across the menu** — A well-planned menu does not repeat the same flavor profiles consecutively. Map each dish on a scale of: richness (light to heavy), acidity (bright to muted), spice level (mild to bold), and cooking method (roasted, braised, raw, fried). Adjacent courses or consecutive days should contrast.
7. **Calculate food cost for each item** — For each dish, calculate the food cost percentage: (ingredient cost ÷ selling price) × 100. Target 28-35% for restaurant menus. Items above 35% require repricing or portion adjustment; items below 20% may be underportioned or low-value. For institutional menus, cost per meal must align with reimbursement rates or budget allocations.
8. **Evaluate equipment and labor load** — Map each dish to the equipment and skilled labor it requires. A menu where every dish requires the grill station at the same time creates service failure. Distribute dishes across oven, sauté, grill, and cold prep stations. Similarly, distribute labor-intensive prep across the week for institutional menus.
9. **Plan for ingredient cross-utilization** — Identify ingredients that appear in multiple dishes. Cross-utilization reduces purchasing complexity and waste. Example: roasted chicken serves as entrée on Monday, in a grain bowl on Tuesday, in a soup on Wednesday. This is menu engineering, not repetition.
10. **Test, collect feedback, and revise** — Run the menu for a defined trial period (2 weeks for institutions; a full service cycle for restaurants). Track: which items sell fastest, which are returned, food cost actuals vs. projections, and any complaints about nutritional balance or variety. Revise based on data, not assumption.
## Rules
- The menu drives purchasing — finalize the menu before ordering; purchasing before menu planning leads to cooking to inventory rather than cooking to plan.
- Nutritional balance is measured across the full day or week, not per individual dish — a rich entrée is acceptable if the rest of the day's meals are nutritionally lighter.
- Never plan beyond available equipment capacity — a dish requiring equipment not in the kitchen is not a menu item, it is a capital expenditure request.
- Build in at least one simple, low-cost, high-margin item in every menu section — this item carries food cost for more expensive items and ensures the average stays in range.
## Common Mistakes
- **Planning dishes before establishing constraints** — designing aspirational menus that exceed the kitchen's equipment, staff skill, or ingredient availability; constraints must define the design space before ideation begins.
- **Ignoring cross-utilization** — treating every dish as independent increases purchasing volume, storage requirements, and waste; deliberate ingredient overlap is economically and operationally essential.
- **Balancing individual dishes instead of the full menu** — every individual item does not need to be nutritionally complete; the menu as a whole provides balance when properly planned.
- **Setting price points before calculating food cost** — pricing by feel or market comparison without calculating actual ingredient cost leads to structural unprofitability that cannot be corrected without a menu overhaul.
## When NOT to Use
- Single-occasion improvisational cooking where no repeatability is needed and no operational constraints apply.
- Emergency or crisis food service where speed and available inventory supersede planning — in this context, improvisation from inventory is necessary and appropriate.
- Specialty therapeutic diet planning requiring clinical dietitian oversight — this skill provides framework; complex renal, oncology, or allergy-managed menus require licensed practitioner involvement.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!