# Office Hours

YC-style office-hours diagnostic. Surfaces forcing questions, challenges premises, lands on a sharper problem statement before any code is written.

## How it runs

| # | Step | Who runs it | What happens |
| --- | --- | --- | --- |
| 1 | Kickoff | Meester | Hear the user out. Capture the problem they think they're solving in their own words. No solutioning yet. |
| 2 | Challenge | Meester | Stress-test premises. What assumption is doing the most load-bearing work here? |
| 3 | Reframe | Meester | Generate 2-3 alternative framings of the problem. The user picks one to focus on. |
| 4 | Lock scope | Meester | Write the scope down. One paragraph. Two if forced. Hand off to plan-review next. |

Say something like "office hours" or "scope this" or "help me think about" or "what should I build" in chat to start it.
