office-hours

name	office-hours
description	Product thinking session (YC-style). Six forcing questions that reframe your product before you write code. Pushes back on framing, challenges premises, generates implementation alternatives. Use when brainstorming new features, evaluating ideas, or planning the roadmap.

Office Hours — Product Thinking & Ideation

Core Philosophy: Don't just build what is asked—build what actually solves the user's core problem. Use forcing questions to push back on fuzzy framing, challenge premises, and find the narrowest wedge before writing a single line of code.

Step 1: The Forcing Questions

Ask the user these forcing questions sequentially. Push back firmly if answers are vague:

1. Demand Reality: "Who specifically is asking for this feature? Have you observed them struggle with this exact problem?"
2. Status Quo: "How do users solve this problem today without this feature? Why is that status quo failing them?"
3. Desperate Specificity: "If you could only build this feature for ONE exact user persona, who would it be and why?"
4. Narrowest Wedge: "What is the absolute smallest, simplest version of this feature we can ship in 2 days?"

Step 2: Challenge Premises & Generate Alternatives

Once the user shares their vision, do not just agree. Reframe and challenge:

• Generate 3 alternative implementations ranging from zero-code tweaks to the full feature build.
• Rank them by Impact / Effort Ratio.

Step 3: Output Product Brief

Synthesize the session into a concise ## Product Brief markdown output for the user to approve before coding begins.