What problem does it solve? Founders and builders often jump straight to code before validating whether anyone actually wants the thing. This Skill forces a structured diagnostic conversation — demand evidence, status quo, narrowest wedge — before any implementation, and captures the result as a design document. ## Core Features & Use Cases - Startup Mode: Six YC-style forcing questions (demand reality, status quo, desperate specificity, narrowest wedge, observation, future-fit) asked one at a time with pushback until answers are specific and evidence-based. - Builder Mode: Design-thinking brainstorming for hackathons, side projects, learning, and open source work. - Design Doc Output: Saves a design document per project; explicitly refuses to write code or invoke implementation skills. - Use Case: You have a new product idea and want to know if it is worth building. Run office hours before any planning or coding to stress-test demand and scope the smallest viable wedge. ## Quick Start Ask the assistant to run office hours on your new product idea before writing any code.