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 that exposes weak demand evidence, vague markets, and missing wedges before any implementation begins. ## Core Features & Use Cases - Startup Mode: Six forcing questions covering demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit, asked one at a time with pushback until answers are specific and evidence-based. - Builder Mode: Design-thinking brainstorming for side projects, hackathons, learning, and open source work. - Design Doc Output: Saves a design document to the project directory instead of writing code, with a hard gate against implementation. - Use Case: You have an idea for a developer tool. Run office hours before writing code; the skill challenges your demand evidence, identifies your narrowest paying wedge, and produces a design doc you can hand to /plan-ceo-review or /plan-eng-review. ## Quick Start Ask the assistant to run office hours on your new product idea and answer the forcing questions to produce a design document.
