brainstorming

To clarify complex software requests before writing code, use a Socratic questioning protocol that dynamically generates context-aware questions about purpose, users, and scope to prevent implementation on misunderstood requirements.

Socratic questioning for requirements gathering is a protocol that enforces a minimum of three clarifying inquiries on complex requests to define scope and ensure clarity before task execution begins.

You should ask a minimum of three clarifying questions for ambiguous feature requests to successfully establish the feature's purpose, target users, and must-have scope before any implementation starts.

Yes, this requirements gathering approach works for large scale complex requests by dynamically generating context-aware questions based on the request domain, features, and scale to ensure proper scope definition.

To handle error reporting and progress reporting during requirements clarification, the Socratic questioning protocol provides structured status updates and error handling while it dynamically evaluates the request domain.

You should not use Socratic questioning for software engineering tasks when the request is already unambiguous, as the protocol enforces a minimum of three clarifying inquiries which would unnecessarily delay straightforward task execution.