brainstorming

To define technical requirements before coding, use Socratic questioning to clarify user intent, explore optioneering with trade-offs, and verify designs incrementally. This process refines vague requests into validated design specifications before implementation begins.

The Socratic method for software design involves asking targeted questions to explore user intent and refine requirements. It helps break down architectural changes into manageable chunks, ensuring design specifications are validated incrementally through optioneering and trade-off analysis.

Explore technical approaches by proposing multiple options and discussing their specific trade-offs. This optioneering process ensures architectural changes are evaluated against requirements, allowing you to verify designs incrementally and output validated specifications to documentation files.

Yes, Socratic questioning refines vague feature requests by asking targeted questions to clarify user intent. It breaks down the design into manageable chunks for incremental approval, ultimately producing validated design specifications output to documentation files.

Use a brainstorming process when you need to clarify user intent and design choices before starting implementation. It prevents wasted development effort on misunderstood tasks by validating requirements and technical approaches through Socratic discovery and optioneering.