executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
menu-cost-engineerCost a menu item to a plate cost and food-cost percentage, then price it for a target margin. Use when asked to cost a dish, calculate food cost percentage, price a menu item, or engineer a menu for profitability. Produces a plate-cost breakdown (ingredient × yield × price), the food-cost %, a suggested price for the target margin, and menu-engineering flag…
Independent GitHub snapshot · Automated classification · Original documentation governs
Restaurants don't fail on bad food — they fail on math they never did. A dish that "feels" priced right can quietly run a 45% food cost. This skill costs the plate honestly (accounting for yield loss and waste), sets a price to the margin the operator actually needs, and flags where the menu is leaking money.
Given a recipe and ingredient prices, produce the full costing — estimate yields and waste where not given (label the assumption). If prices are missing, ask or use a stated regional estimate and flag it.
Ask for (if not provided, else infer and label):
| Ingredient | As-purchased cost/unit | Yield % | Portion | Plate cost |
|---|---|---|---|---|
Include a line for waste/trim and any garnish/consumables.
Given popularity (if provided) and margin, classify: Star (high both — feature it), Plow-horse (popular, low margin — reprice/re-engineer), Puzzle (high margin, low sales — promote/reposition), Dog (low both — cut or rework).
2–3 concrete moves — portion, spec, supplier, price, or plate composition — to hit the target without hurting the guest experience.