brainstorming

Requirements gathering and idea refinement are facilitated through a structured dialogue that explores user intent, clarifies project scope, and defines constraints to prevent premature implementation. This ensures a validated design document is created before coding begins.

Exploring design approaches involves proposing 2-3 distinct implementation options with their respective trade-offs, then recommending the most suitable choice. This allows you to evaluate architectural patterns and user flows before committing to a specific implementation path.

The design presentation process breaks down detailed specifications into incremental sections for user approval. This collaborative approach ensures stakeholder buy-in is achieved at each stage before transitioning to the implementation planning phase.

Yes, you can use this to plan a new user authentication feature from scratch by exploring project context and answering clarifying questions. It guides you through defining purpose, constraints, and success criteria before any implementation actions are taken.

A structured brainstorming approach should be avoided when implementation must begin immediately without validated specifications, or when a project modification is trivial and requires no exploration of user intent, design options, or architectural trade-offs.