Preview — full styling will appear after the next deploy completes.

bmad-method

Brainstorming

Generating options before committing to an approach

BMAD Brainstorming is a structured diverge-then-converge session where multiple personas generate solution options before the team commits to any one approach. It prevents premature lock-in and surfaces alternatives the original author did not consider.

flowchart TD
    PR([Problem or Story]) --> DIV[Diverge Phase<br>no critique, all options valid]
    DIV --> OP1[Architect Options<br>technical approaches]
    DIV --> OP2[PM Options<br>story framings]
    DIV --> OP3[Developer Options<br>implementation paths]
    OP1 --> CON[Converge Phase<br>evaluate against constraints]
    OP2 --> CON
    OP3 --> CON
    CON --> SE{Single option<br>selected?}
    SE -->|Yes| RD([Chosen approach<br>with rejection rationale])
    SE -->|No| DC[Document split decision<br>for human review]

The most common failure mode in AI-driven development is committing to the first plausible solution. The AI produces a coherent approach, it looks reasonable, and implementation begins — but no one checked whether a simpler option existed, or whether a known constraint would have ruled out the chosen approach. BMAD Brainstorming inserts a structured options-generation step before any approach is locked in.

The session runs in two phases. In the diverge phase, each relevant persona generates one or more alternative approaches independently — without critiquing the others. The Architect generates technical options; the PM generates story-level framings; the Developer generates implementation paths. The constraint is: during diverge, all options are valid, no option is rejected, and the goal is quantity over quality.

In the converge phase, the team evaluates the generated options against the known constraints: technical feasibility, scope, dependencies, and time. The output is not necessarily the best option — it is the chosen option with a documented rationale for why the alternatives were rejected. That rationale is what makes the decision reviewable and reversible if constraints change.