brainstorm

Brainstorming technical decisions involves a multi-phase process that scouts the codebase, evaluates approaches with explicit pros and cons, and challenges assumptions to prevent costly wrong turns during system design or feature exploration.

It compares architecture options by applying YAGNI, KISS, and DRY constraints, explicitly challenging assumptions to produce a decision-ready markdown summary of viable options, validation criteria, and next steps.

Brainstorming technical decisions generates decision-ready markdown reports capturing options, pros/cons, risks, and next steps, strictly avoiding actual code implementation to focus solely on feasibility and trade-off evaluation.

You need a risk analysis and trade-off assessment before feature implementation when facing ambiguous or stuck development problems, ensuring you evaluate system design options and feasibility to avoid costly wrong turns.

Yes, you can use this structured ideation process for technical debates, system design, and feature exploration, as it guides a multi-phase flow from scouting the codebase to reaching a risk-aware consensus without writing code.