yet-another-meal-planner-deployment

Plan meals — a week, a few days, tonight, or around a market haul. Use for "make me a menu", "what should we eat this week", "what's for dinner", "plan around what's in the fridge", and side questions like "what goes with the short ribs". Reads kitchen context, renders the interactive week card (the engine composes, the card presents and commits), rounds out plates, and reviews what needs buying.

Walk the household through cooking hands-free, or capture a meal already made. Use for "I'm making the arroz caldo", "walk me through dinner", "let's cook" — and equally for "I made the chili last night", "we ate the leftovers". One flow owns the cooking log.

Record what's physically in the kitchen. Use for "we're out of olive oil", "put 3 lb of beef in the freezer", "used the last of the parmesan", "picked up basil and tomatoes at the market". Merges instead of duplicating. A haul the household wants cooked from is a planning request.

File a bug to the maintainer when something is genuinely wrong — a failing action that can't be routed around, repeated corrections on the same point, or the member saying it's broken.

First-run setup, or reviewing what's saved. Use for "get me set up", "onboard me", "update my profile", "what do you know about me", or when the profile reads empty. Three areas and done — everything else is learned through use or managed in the app.

Flush the list — order online, walk a store, or hand off. Use for "place the order", "I'm headed to the store", "give me a shopping list", "shop it on Instacart", "I'm at Central Market". Capture is continuous; this flow is the deliberate flush, branch picked from the household's setup and this trip's words.

Internal shared rules for yamp, loaded by reference from the workflow skills (via their prerequisite line). Not invoked on its own.