What problem does it solve? Founders and builders often jump into coding before validating whether an idea is worth pursuing. This Skill runs a structured YC-style office hours session that stress-tests demand, target users, and premises before any code is written, then captures the outcome in a durable design document. ## Core Features & Use Cases - Two brainstorming modes: Startup mode applies six forcing questions (demand reality, status quo, narrowest wedge, future-fit); Builder mode supports design-thinking exploration for side projects, hackathons, and open source. - Design doc generation: Writes a structured design document to ~/.gstack/projects/ with problem statement, premises, approaches considered, and success criteria, including a supersedes chain across revisions. - Adversarial spec review loop: Dispatches an independent reviewer subagent to score the document on completeness, consistency, clarity, scope, and feasibility before user approval. - Use Case: You have an idea for a developer tool and ask "is this worth building?" The Skill walks you through demand evidence and wedge definition, challenges your premises, and saves an approved design doc that downstream planning skills can consume. ## Quick Start Ask the assistant to run office hours to brainstorm and pressure-test your new product idea before writing any code.
