office-hours

Product idea validation involves testing demand reality, current alternatives, and urgency through forced-question probing. This skill guides you through structured brainstorming to determine whether to pursue, refine, or drop your concept before any code is written.

Structured brainstorming for an early-stage product concept uses a founder interview format with forced-question probing and branch-aware context gathering. This process turns vague excitement into concrete scope and wedge questions, producing a design doc for downstream review.

Yes, you can use the builder brainstorming mode for side projects, hackathons, learning, and open source concepts. It applies the same structured interview and design-doc creation process without requiring a full startup strategy commitment.

Creating a design document from an open-ended product discussion requires branch-aware context gathering and forced-question probing. This skill synthesizes the conversation into a durable design doc and hands it off to downstream review skills as an actionable plan.

Idea validation works for go-or-no-go decisions by applying founder rigor to test demand reality and the narrowest viable wedge. It helps you decide whether to pursue, refine, or drop an existing startup concept before committing development resources.

You should avoid using a structured founder interview when you already have a validated design doc and need implementation, or if your project requires coding immediately without prior scope definition, as this skill focuses strictly on pre-code validation and strategy.