Meal Planning
A .menu file lets you plan meals across multiple days, reference recipes from your collection, and generate a combined shopping list for the entire plan.
.menu files work in CookCLI (cook recipe, cook shopping-list) and the Cook Editor, which renders them as a week view with a combined shopping list. Apps that recognise dated sections can surface today's menu.
Example Menu File
Here's a real three-day plan from an actual Cooklang cookbook:
How Menu Files Work
Recipe references like @./Breakfast/Mexican Style Burrito{2%servings} point to .cook files in your recipe directory. When generating a shopping list, the system pulls all ingredients from the referenced recipes.
Direct ingredients like @filter coffee{1%cup} work for simple items that don't need a full recipe.
Scaling is built in. {2%servings} adjusts recipe quantities for the number of people. {1/2} means half of a batch recipe.
Day sections (==Day 1==) organize meals chronologically.
Notes (> do prep for burrito) add reminders about timing and logistics.
Snacks and batch prep sections ensure these items appear on the shopping list too.
Reusing Ingredients Across Days
Notice how this plan reuses elements efficiently:
- Mexican Style Burritos appear on two mornings — worth prepping in bulk
- The Boring Salad accompanies different mains, using up fresh greens
- Beef stew is made in advance and portioned across meals
- Coffee and tea quantities reflect daily consumption
This reduces both prep time and waste.
See Also
- Shopping Lists — Generate lists from your meal plan
- Pantry Management — Exclude items you already have
- CookCLI Commands — Full command reference