brainstorming

Structured brainstorming transforms vague ideas into concrete requirements through one-question-at-a-time dialogue. Answer guided questions about goals, scope, and approach to progressively clarify what to build and how to build it, with design sections delivered after each step for validation.

Use brainstorming during Phase 2 (Requirements) and Phase 3 (Design) when you have a rough idea but are unsure about scope, approach, or functional and technical requirements. It's applied when requirements are unclear and need collaborative refinement through option exploration.

Brainstorming presents 2-3 approaches for each design decision, with explicit trade-offs between them. Each option is documented with 200-300 word design sections so you can evaluate and validate before proceeding, supporting decisions about architecture and implementation strategy.

Yes. The brainstorming process conducts web research using WebSearch and WebFetch, explores APIs with Bash curl, and builds structured documentation. This grounds vague ideas in real-world examples and technical feasibility before finalizing designs.

Incremental validation through one-question-at-a-time inquiry clarifies goals progressively. Each response includes design sections for review, allowing you to iteratively refine scope and approach until requirements and design are concrete enough to implement.