brainstorming

Structured brainstorming guides you through phases of understanding the problem, exploring 2-3 alternative solutions, and validating designs incrementally before implementation. This approach captures requirements upfront, prevents scope creep, and ensures alignment across teams, reducing costly rework later.

Brainstorming converts rough ideas into fully-formed designs by asking targeted questions to refine concepts, examining the existing project state, exploring alternatives, and documenting the final design in a permanent record. The result is a clear, validated plan ready for implementation.

Use structured questioning during early-stage ideation for any new feature, product, or architecture decision. It's essential when requirements are unclear, stakeholder alignment is uncertain, or multiple solution paths exist—situations where upfront validation saves development time.

Autonomous reconnaissance inspects existing project state—repos, docs, commits—to form an initial understanding before asking questions. This context-aware approach ensures your design questions and alternatives are grounded in your actual system, avoiding disconnected or redundant solutions.

Yes. Brainstorming applies across product development, software architecture, workflow design, and planning tasks. Wherever you face design choices early in the project lifecycle, structured questioning and alternative exploration ensure a solid foundation before implementation.

Brainstorming produces design artifacts including design documents, implementation plans, and roadmaps. These are written to a permanent docs/ location after validation, creating an audit trail and reference for the team throughout the project lifecycle.