brainstorm

To document architecture decisions, you need a structured brainstorming process that captures requirements, explores options, and records the rationale. This approach produces an ARCHITECTURE.md file containing the final design, trade-off analysis, and component breakdown.

Collaborative architecture design works best with discovery-driven brainstorming that guides teams through requirements gathering, option exploration, and iterative refinement. This ensures all constraints are understood before finalizing the design and documenting the component breakdown.

Yes, collaborative brainstorming is specifically designed for feature planning, system redesigns, and technology evaluations. It guides discovery and trade-off analysis to help teams evaluate multiple architectural approaches before committing to a final design.

An ARCHITECTURE.md file should contain the final design, rationale for decisions made, and a detailed component breakdown. It is generated through iterative refinement after exploring multiple architectural options and analyzing their trade-offs.

Discovery-driven brainstorming works by first understanding your requirements and constraints, then exploring multiple architectural approaches. It applies structured trade-off analysis during feature planning to guide teams toward an informed final design decision.