system-brainstorming

To translate ambiguous ideas into validated design specifications, use a structured pre-implementation conversation to surface intent, constraints, and success metrics through iterative questioning and proposed approaches.

The best way to clarify requirements is using a one-question-at-a-time approach to refine purpose, constraints, and success metrics, preventing wasted implementation effort caused by unclear assumptions.

To compare approaches for feature design, propose 2–3 viable options with clear trade-offs and a recommended path, ensuring decision-making is based on validated constraints before implementation.

Yes, you can use guided brainstorming for UI/UX changes, small utilities, and curriculum planning where scope and success criteria must be clarified through iterative questioning before coding.

To enforce a design approval gate, require presenting a documented design file and obtaining explicit user approval before any implementation actions, ensuring development starts from a validated design.

Exploring project context matters because inspecting project files, documentation, and recent changes ensures clarification questions are relevant and grounds proposed approaches in existing project realities.