brainstorm

Guided brainstorming transforms vague ideas into commit-ready design documentation by applying a stepwise workflow to define constraints, evaluate approaches, and draft design sections. It outputs documentation-ready plans directly to a .brainstorm/plans directory.

The best way to structure collaborative brainstorming uses stepwise questioning with one question per message to refine ideas without overwhelming the team. It evaluates 2-3 design approaches with trade-offs before presenting a recommended path.

Stepwise ideation works by identifying the core goal and intended user outcome, then delivering design segments in focused 200-300 word chunks. This maintains readability while ensuring all outputs are documentation-ready.

Yes, you can use this brainstorming workflow to generate a plan file for git version control. It creates a plan file under .brainstorm/plans and prepares a commit-ready design that can be pushed directly to your repository.

Yes, the ideation process supports evaluating multiple design approaches by proposing 2-3 design options with specific trade-offs. It then presents a recommended path to align on success criteria before implementation begins.

You should use guided brainstorming when you have a vague idea requiring structured requirements gathering and success criteria alignment. It captures collaborative input and defines constraints before committing to a specific implementation path.