Restaurant Musk First-Principles Analysis

Problem Addressed

Restaurant and store operations often stall on “experience-driven” decisions: menu selection, pricing, scheduling, inventory, and complaint handling all rely on intuition, but lack a repeatable breakdown path. This skill turns Musk first-principles thinking into a workflow that moves a business issue from vague description to quantified, assigned, and reviewable actions.

How It Works

It does not return a universal answer. Instead, it runs a four-step process:
- Problem definition: identify the stage goal, constraints, and missing data;
- Framework matching: load method-core.md, method-application.md, or method-advanced.md as needed, avoiding overloading the context;
- Solution ranking: output Top3 priority actions with “who does it, what it is, and when it shows impact”;
- Execution review: fill checklist-quick-start.md and template-analysis.md with key metrics, then set 2-4 week checkpoints.

Boundaries

It fits diagnostics and planning for restaurant, chain, and store operations in business-ops, but it does not fill missing data for you. High-stakes financial, legal, or supply-chain judgments should be reviewed by the responsible specialist, especially where assumptions are based on industry or theoretical baselines.