brainstorming

Transforming rough ideas into validated designs requires a structured, question-driven workflow that explores 2-3 architectural approaches, gathers constraints, and incrementally validates sections with stakeholders to prevent assumptions and rework.

The best way to brainstorm architecture for unclear features is by enforcing a strict question budget per phase to elicit missing success criteria, then generating 2-3 design approaches with trade-offs and a clear recommendation.

You validate product design proposals by presenting designs in sections for stakeholder approval, applying phase-lock rules to control the workflow, and writing finalized design documents to docs/plans/ for audit evidence.

Yes, the design validation process requires repository reconnaissance including listing files, checking git log, and inspecting the README to understand existing constraints and preserve audit evidence during feature ideation.

The brainstorming workflow hands off to writing-plans and using-git-worktrees by finalizing the validated design document in docs/plans/ and transferring these artifacts for downstream documentation creation and code implementation.