brainstorming

Brainstorming refines rough ideas into structured designs through guided questioning and collaborative dialogue. Start with your project context, ask clarifying questions to explore the concept, then validate incrementally by presenting 2-3 design options with trade-offs before committing to implementation.

Use guided questioning and incremental validation to break vague concepts into concrete design directions. Present multiple approaches with trade-offs, gather feedback one question at a time, and document architecture, data flow, and error handling considerations as you refine the idea.

Architecture planning through brainstorming presents design options with explicit trade-offs, validates concepts incrementally through dialogue, and produces documented architecture and data flow outputs. This collaborative approach identifies constraints and design considerations before development begins.

Yes. Brainstorming proposes 2-3 approaches with trade-offs for a single feature or concept, presenting each as a 200-300 word design section. This lets you compare architecture, data flow, and error handling strategies side-by-side and validate which direction fits your project scope.

Prepare your current project context—existing architecture, tech stack, constraints, and the vague feature or problem you want to refine. Having this context ready helps guide focused questioning and ensures design options align with your existing system rather than proposing disconnected alternatives.