office-hourslisted

# Office Hours ## Core Rule Force product validation before code via uncomfortable questions. Stop the user from coding if the problem isn't clear. ## When to Use Invoke with `/office-hours` when: - Starting a new feature and want to validate the approach before coding - Unclear requirements — need to sharpen the problem statement - Multiple possible solutions and need to pick one deliberately - Want to prevent building the wrong thing fast - Before creating a technical plan or writing a contract ## Process ### Phase 1: Problem Statement Force a clear articulation of the problem: 1. **What problem are we solving?** — One sentence, no jargon 2. **Who has this problem?** — Specific user type, not "users" 3. **How do they solve it today?** — Current workaround or pain point 4. **How will we know it's solved?** — Observable outcome, not a feature list 5. **What happens if we don't solve it?** — Impact of inaction Ask the user each question individually. Do not proceed until all 5 are answered clearly. If an answer is vague, push back with a specific follow-up. ### Phase 2: Solution Validation Challenge the proposed solution: 1. **Is this the simplest solution?** — What's the minimum that solves the problem? 2. **What are we NOT building?** — Explicit scope exclusions 3. **What assumptions are we making?** — List them, then question each one 4. **What's the riskiest assumption?** — The one that, if wrong, makes everything else moot 5. **How can we test the riskiest as