Dining Jobs Product Philosophy

What Problem It Solves

In restaurant and consumer operations, the hard part is often not generating ideas, but connecting ideas, data, priorities, and execution. This skill turns Jobs-style product philosophy into an executable analysis framework: define the key problem, match a method, then output prioritized actions and review checkpoints. It fits product positioning, store operations strategy, and process improvement discussions that need structured judgment rather than open-ended brainstorming.

How It Works

The skill follows a four-step workflow:
- Problem definition and information gathering: clarify the current core issue and organize the background data provided.
- Framework matching and deep analysis: load relevant methods from references/, including core, application, and advanced guides, only when needed.
- Solution generation and prioritization: output top actions using a “numbers first, tiered presentation” style, and make them executable: who does what by when.
- Execution and review: use templates such as assets/checklist-quick-start.md and assets/template-analysis.md, and set 2-4 week review checkpoints.

Boundaries and Notes

The skill emphasizes transparent assumptions: when real data is missing, it may use industry or theoretical baselines, which should be labeled clearly. It works best when the input includes measurable business context. If the request is only a vague goal, basic facts such as customer segment, scale, cost, and target should be added first. Case files can inform structure, but they should not be treated as store-specific conclusions.