superpowers-brainstorming

Brainstorming early-stage product ideas into structured design documentation requires an iterative dialogue that elicits requirements, generates design options, and validates concepts in incremental sections. This approach yields a concrete design narrative with architecture and data flow details.

Generating and comparing design options during project ideation is best handled by producing 2-3 options with clear trade-offs. These options are presented in digestible sections of 200-300 words to help teams understand constraints and success criteria before implementation.

Eliciting requirements for software design through collaborative dialogue involves focused questions that refine idea context. This conversational workflow validates progress incrementally, ensuring teams understand intent and constraints before moving to implementation.

Conversational brainstorming can document architecture and component designs by producing a structured design narrative. It validates designs incrementally across sections like architecture, components, data flow, and testing, making them ready for knowledge bases or git repositories.

Limitations of using structured prompts for design ideation include the requirement for disciplined prompt orchestration. The process relies on a conversational workflow presenting designs in sections, typically 200-300 words per section, which demands active iterative validation to maintain progress.

Design ideation does not work optimally without prior technical context. The process requires you to describe your idea and project context to begin the iterative brainstorming dialogue that yields fully formed designs and specs.