brainstorming

Refining ideas into concrete designs involves structured dialogue to clarify requirements, explore multiple approaches with tradeoffs, and validate design decisions incrementally. This skill guides you through targeted questions about constraints and success criteria, then presents alternative solutions so you can make informed choices before implementation.

Use design exploration when requirements are fuzzy, multiple architectural approaches are possible, or you're uncertain about the best direction for a feature. Early structured validation prevents costly rework, ensures team alignment, and produces documented design rationales that guide development.

Evaluating approaches means presenting each option's tradeoffs—performance, scalability, complexity, maintenance—alongside your constraints and success criteria. This skill structures that comparison, asks clarifying questions about your problem space, and helps you document why one approach fits your needs better than others.

Yes. This skill is built for fuzzy requirements and early-stage ideation. It asks targeted questions to uncover hidden constraints, helps you articulate what success looks like, and guides you through exploring alternatives so requirements become clear before design decisions solidify.

Design brainstorming focuses on validating the *what* and *why*—problem definition, architectural options, and tradeoffs—through dialogue. Planning implementation tackles the *how*—specific steps, tools, and timelines. Brainstorming comes first to prevent building the wrong thing well.