cmd-workflow-brainstorm

A design-first brainstorming workflow aligns feature requirements before coding by guiding teams through a phased process of clarifying questions, evaluating constraints, and comparing multiple approaches to reduce rework and scope creep.

Brainstorming architecture options is best handled by a phase-driven workflow that evaluates context and dependencies, presenting two to three viable design approaches with clear trade-offs for team comparison before implementation.

A design approval gate enforces feature planning by acting as a hard block before implementation, requiring explicit design approval and saving validated decisions to a design document before transitioning to implementation planning.

Yes, this design-first workflow fits modifying existing component behavior, building new components, and designing new features by evaluating dependencies and intent through structured questions before any code is written.

To start a design briefing for a new feature, you need to define the problem, intent, and success criteria, then present at least two viable design approaches for evaluation and approval.