🍽️ Food & Beverage Ops · Kitchen Consistency
Engineer the menu on data, not vibes
Popularity × margin matrix driving placement, pricing, and cull decisions each season.
intermediate~40 minChefsF&B ManagersRestaurant Owners
Steps
- 1Classify items: stars (high-high), plowhorses (popular-low margin), puzzles, dogs
- 2Reposition stars to golden zones; rename/rephoto puzzles before cutting
- 3Test price moves ±5% on plowhorses before dramatic changes
- 4Cull dogs ruthlessly but keep one 'traffic anchor' if it drives visits
- 5Watch ingredient crossover — cutting one dish may strand inventory
- 6Repeat analysis every season with same metrics for trend honesty
Common Pitfalls
- ▲Menu redesigns driven by chef boredom instead of matrix
- ▲Margin math ignoring waste and prep labor
Commands
Install with skills CLI
$ npx skills add aniruddhaadak80/skills --skill kitchen-consistency-menu-engineering-cycleInstall globally
$ npx skills add aniruddhaadak80/skills --skill kitchen-consistency-menu-engineering-cycle -gTags
#menu#pricing#profitability#food-beverage#kitchen-consistency