brainstorming

To turn vague ideas into validated design documents, you must iteratively clarify user intent, constraints, and trade-offs. This involves systematically exploring project context and asking focused questions to surface requirements before proposing implementation-ready design plans.

The best way to gather requirements for feature design is through clarifying dialogue. Ask one focused question at a time to surface success criteria and edge cases, then present multiple approaches with trade-offs to ensure shared understanding before implementation begins.

Iterative design validation works by presenting design sections progressively and requiring explicit user approval before any implementation step. This gating mechanism ensures hidden assumptions are resolved and the design document accurately reflects the approved plan.

Yes, you can use this brainstorming process for UI component design, workflow changes, feature proposals, or any scoped engineering task. It explores project context, files, and recent commits to propose recommended design paths and avoid rework.

You should not use a clarifying dialogue approach when you already possess a fully validated design document or when the scoped engineering task requires no trade-off analysis. It is specifically designed for transforming undocumented intent into decision-ready plans.

To start brainstorming a design plan, you need a raw idea and willingness to answer clarifying questions about project purpose, constraints, and success criteria. The process examines context, files, and docs to generate approaches and produce a committed design document.