brainstorming

Brainstorming refines vague ideas into validated designs through structured Socratic questioning. It explores constraints, edge cases, and alternatives, then stores the final design as an immutable epic with requirements, preventing costly rework during implementation.

The brainstorming process proposes 2-3 architectural approaches with explicit trade-offs for each option. This comparative exploration ensures you understand the implications of each choice before committing to implementation.

Incremental design validation presents design sections for approval while research agents document the rationale behind each decision. Validated content stores in structured tasks, creating an immutable record that traces discovery and supports iterative learning.

Use brainstorming for early-stage feature ideas, architecture exploration, and requirement refinement when coding is not yet ready. It's essential when you need to resolve functional or technical requirements upfront and ensure all stakeholders agree before development begins.

Yes. Brainstorming applies to requirements gathering and problem-solving by guiding discovery through guided questioning. It ensures all functional and technical requirements are identified, validated, and documented before implementation planning.