weekly-meal-plan

name	weekly-meal-plan
description	Create a dated weekly meal plan markdown file and consolidated shopping list from this repo's existing recipe markdown files. Use when the user gives a list of meals for the week, asks for a weekly meal plan, grocery list, or shopping list, and the meals must come from recipes in the repo.

Weekly Meal Plan

Workflow

1. Read available recipes from recipes/*.md.
2. Match the user's requested meal names to recipe files. Use forgiving matching for names like "turkey chili" -> recipes/turkey-chili.md.
3. If any requested meal is not represented by a repo recipe, stop and tell the user which meal is missing. Do not invent a recipe inside the weekly plan.
4. Read each selected recipe completely.
5. Create or update a dated markdown file in weekly-meal-plans/ named YYYY-MM-DD-weekly-meal-plan.md, using the current local date unless the user specifies a different date.
6. Include:
   • # Weekly Meal Plan - YYYY-MM-DD
   • ## Meals
   • Assumptions, including per-recipe serving counts or yield notes found in recipe headings
   • Any cross-recipe planning notes, such as shared ingredients or consolidation decisions
   • ## Complete Shopping List
   • ## Recipe Sources
7. Consolidate duplicate ingredients across recipes into one shopping item when practical.
8. If the user asks to ground the list in Fred Meyer products, use fred-meyer-product-grounding after the normal weekly meal plan is complete. Keep Fred Meyer product matches as annotations under shopping-list items.

Consolidation Rules

• Keep individual recipes standalone. Put all cross-recipe coordination only in the weekly plan.
• Combine exact duplicates by summing quantities, such as 1 cup dry brown rice plus 2 cups dry brown rice -> 3 cups dry brown rice.
• Combine compatible produce thoughtfully, such as romaine leaves and chopped romaine into one larger romaine purchase.
• Keep optional items marked optional.
• Preserve brand/store preferences from recipes, such as Fred Meyer, McCormick, or Pace.
• When quantities are vague or package-based, use grocery-practical wording rather than false precision, such as 1 large tub sour cream, or 2 regular tubs.
• Do not browse the web for recipe data unless the user explicitly asks. The meal plan input must be selected from recipes/*.md.
• Do not replace shopping-list items with Fred Meyer products. When product grounding is requested, annotate the existing list instead.

Output Style

• Use checkbox list items for shopping entries.
• Group shopping items by store section when possible:
  • Meat and Seafood
  • Produce
  • Dairy and Refrigerated
  • Canned Goods
  • Grains, Bread, and Crackers
  • Sauces, Seasonings, and Pantry
  • Frozen
• Reference recipe sources as paths like recipes/turkey-chili.md.