brainstorming

Brainstorming facilitates structured ideation through phased questioning, multi-option exploration, and incremental validation. It guides you from initial concept through alternatives and trade-offs to a validated design ready for handoff to implementation planning.

Present 3-5 approaches with explicit trade-offs and a recommended choice highlighted. This structured comparison drives principled decision-making by making trade-offs visible and reasoning transparent before committing to code.

Break designs into 200-300 word sections and present them as discrete chunks for feedback. This phased approach allows team validation at each stage rather than revealing the full design at once, catching misalignment early.

Yes. Brainstorming integrates MFB domain patterns—principals, distributors, operators, opportunities—and engineering principles to structure feature ideation and alternative exploration specifically within CRM workflows.

After design validation is complete and trade-offs are agreed. Brainstorming explicitly hands off to /write-plan, which translates the validated design into actionable implementation steps and specifications.

A rough idea or problem statement is enough. Brainstorming asks structured questions to clarify intent, explore alternatives, and surface assumptions—you don't need a fully-formed brief before starting.