From pm-hospitality
Costs menu items to plate cost and food-cost percentage, then prices for a target margin. Produces ingredient-level breakdowns, menu-engineering flags, and actionable levers.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-hospitality:menu-cost-engineerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-hospitalityGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.