What problem does it solve? Founders and builders often jump straight into coding before validating whether an idea is worth building. This Skill runs a structured office-hours session that interrogates demand, target users, and premises, then produces a design document instead of code. ## Core Features & Use Cases - Dual-mode diagnostic: Runs a YC-style startup interrogation for founders or an enthusiastic design-partner session for hobbyists, hackathon participants, and learners. - Six forcing questions: Pushes on demand evidence, status quo workarounds, user specificity, narrowest paid wedge, observed user behavior, and future-fit, one question at a time. - Premise challenge and alternatives: Forces agreement on premises, then generates 2-3 implementation approaches with effort, risk, and a recommendation. - Design doc output: Saves a structured design document to memory with problem statement, demand evidence, approaches, and one concrete next action. - Use Case: A founder with a SaaS idea invokes the skill before writing code; the session reveals their target user is vague, narrows the wedge to one paid feature, and produces a design doc with a concrete customer-interview assignment. ## Quick Start Ask the assistant to run office hours on your new product idea and help you decide whether it is worth building before writing any code.
