What problem does it solve? Founders and builders often jump straight into code before validating whether anyone actually wants what they are building. This Skill runs a structured YC office-hours-style diagnostic that forces specificity about demand, users, and scope before any implementation begins, and saves the outcome as a design document. ## Core Features & Use Cases - Startup Mode Diagnostic: Six forcing questions covering demand reality, status quo workarounds, desperate specificity, narrowest wedge, user observation, and future-fit, asked one at a time with pushback on vague answers. - Builder Mode Brainstorming: Design-thinking collaboration for hackathons, side projects, learning, and open source ideas. - Design Doc Output: Produces a saved design document instead of code, with a hard gate preventing any implementation action. - Use Case: A founder says "I have an idea for an AI tool for developers." The Skill asks who specifically needs it, what they do today instead, and what the smallest paid version would be, then records the validated concept as a design doc before any planning or coding skills run. ## Quick Start Ask the assistant to run office hours to brainstorm and pressure-test your new product idea before writing any code.
