bridge-failing-menu-rescue

Diagnoses declining menu items and orchestrates rescue, removal, or promotion with effect verification.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/Techno-Rocky/rocky-regi-plugins --skill bridge-failing-menu-rescue-techno-rocky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bridge-failing-menu-rescue
Source: https://github.com/Techno-Rocky/rocky-regi-plugins/tree/main/plugins/rocky-ops/skills/bridge-failing-menu-rescue
Command: npx skills add https://github.com/Techno-Rocky/rocky-regi-plugins --skill bridge-failing-menu-rescue-techno-rocky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a restaurant manager notices a dish that used to sell well has stopped selling, this Skill prevents knee-jerk reactions like blind discounting. It distinguishes genuine slowdown from a structurally dead item using measured POS data, generates hypotheses about why customers skip it, branches into the right intervention (visual refresh, removal, or promotion), and always returns to verify whether the action actually worked. ## Core Features & Use Cases - Slowdown vs. dead-item classification: Uses store insights, dead-menu detection, menu engineering quadrants, basket analysis, and cancellation reasons to determine whether a dish is genuinely declining or was never viable. - Hypothesis generation via synthetic consumer research (SSR): Builds personas from real customer attributes and maps their reactions to anchors like price, appearance, or lack of demand, clearly labeled as reference hypotheses rather than facts. - Branched intervention with approval gates: Routes to visual refresh (AI-generated imagery with compliance checks), irreversible removal (owner publish approval required), or promotion (LINE coupons with mandatory holdout groups). - Closed-loop effect verification: After 7-14 business days, measures lift, holdout, and confidence via campaign ROI and intervention-effect tools, rolling back if results are not significant. - Use Case: A manager asks why the seasonal pasta stopped selling. The Skill confirms it is a true slowdown (not a dead item), finds pricing headroom, generates SSR hypotheses pointing to weak visual appeal, produces a new photo for approval, relaunches with a holdout coupon, and schedules an ROI check two weeks later. ## Quick Start Ask the assistant why a specific menu item has stopped selling recently and what to do about it, then follow the proposed diagnosis and intervention plan.

Frequently Asked Questions about bridge-failing-menu-rescue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find out why a menu item stopped selling?▼

The Skill first checks measured POS data: recent sales trends, menu engineering quadrant, basket co-purchase patterns, and cancellation reasons. It then adds synthetic consumer research hypotheses about price, appearance, or demand, clearly labeled as reference only, before recommending an intervention.

How to tell if a dish is declining or just a dead menu item?▼

The Skill compares recent sales history against dead-menu thresholds. An item that sold well until a specific point is classified as a slowdown worth rescuing, while one that never sold is a structurally dead item routed directly toward removal.

Does the synthetic consumer research reflect real customer opinions?▼

No. SSR output is a model-generated hypothesis based on real customer attribute distributions, not actual customer statements. Without an embedding connector, scores are shown as strength levels rather than numeric percentages, and measured POS data always remains the primary basis for decisions.

Can the Skill remove a menu item automatically?▼

No. Removal via inventory and visibility changes is irreversible, so the Skill must present the target, impact scope, and rollback procedure to the owner and obtain explicit publish approval before executing anything.

How is promotion effectiveness measured after a menu rescue?▼

Coupon distributions are always designed with a holdout group. After 7-14 business days, the Skill checks campaign ROI (lift, holdout, confidence) and intervention-effect significance, and honestly reports when confidence is too low to judge.

What happens if image generation or embedding connectors are not connected?▼

Without an image-generation connector, the Skill stops at presenting prompt candidates instead of producing visuals. Without an embedding connector, SSR results are treated as qualitative model estimates expressed as strength levels, never as measured-looking decimals.