arc-brainstorming

Structured brainstorming explores software architecture ideas before code by guiding you to define project context, ask clarifying questions sequentially, and propose 2-3 solution approaches with trade-offs to prevent rushed designs.

Gathering project requirements for a new feature is best done through structured design exploration that enforces the "no design without exploration" principle, asking targeted clarifying questions one at a time to validate assumptions.

Validating design assumptions to avoid technical debt involves presenting proposed designs in digestible sections and seeking user confirmation at each step, ensuring no implementation begins without thorough exploration.

Yes, structured brainstorming compares multiple solution approaches by proposing 2-3 distinct options with clear trade-offs, allowing you to evaluate different architectural paths before committing to an implementation.

You should not use an exploratory design process when the YAGNI (You Aren't Gonna Need It) principle dictates that a feature is unnecessary, though skipping exploration entirely risks accumulating technical debt from rushed designs.