office-hours

Run a structured diagnostic that asks six forcing questions: demand evidence, current workarounds, the specific user, the narrowest paid wedge, observed user behavior, and future relevance. The office-hours skill asks these one at a time and pushes past vague answers until responses are specific and evidence-based.

Core questions cover demand reality (who would be upset if it disappeared), status quo (what users do now), desperate specificity (name the exact person), narrowest wedge (smallest paid version this week), observation surprises, and future-fit. This skill implements all six with stage-based routing.

Yes. Builder mode handles hackathons, open source, learning, and fun projects with an enthusiastic design-partner posture instead of the hard diagnostic. The skill asks your goal first and routes to the appropriate mode automatically.

No. It has a hard gate prohibiting any implementation skill, code writing, or scaffolding. Its only output is a design document, intended to run before planning or engineering review skills.

The skill offers an escape hatch: after one pushback it asks the two most critical questions for your product stage, and after a second pushback it proceeds directly to the premise challenge and alternatives phases. Full skips require existing evidence like users or revenue.