What problem does it solve? Founders and builders often jump into coding before validating demand, defining a narrow wedge, or stress-testing premises. This Skill runs a YC-style office hours conversation that forces clarity on demand evidence, target users, and approach trade-offs before any code is written, then captures the outcome as a versioned design doc. ## Core Features & Use Cases - Two brainstorming modes: Startup mode applies six forcing questions (demand reality, status quo, narrowest wedge); Builder mode supports design thinking 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 doc on completeness, consistency, clarity, scope, and feasibility, fixing issues across up to 3 iterations. - Use Case: A developer says "is this worth building?" about an AI note-taking idea. The skill challenges their premises, forces a narrow wedge definition, saves a design doc, and hands off to /plan-eng-review for architecture lock-in. ## Quick Start Ask the assistant to run office hours to brainstorm and pressure-test your new product idea before writing any code.
