brainstorming

To clarify ambiguous project requirements before development, use a Socratic questioning protocol that dynamically generates context-based questions to identify decision points and architectural trade-offs. This ensures alignment and prevents wasted implementation effort.

The Socratic method for requirements gathering involves triggering structured questions about purpose, users, and scope for new features. It guides stakeholders through decision points, presenting options with clear architectural consequences and default choices.

You identify architectural trade-offs during communication by dynamically generating targeted questions based on request context. This structured questioning approach exposes critical decision points and presents available options with their specific architectural consequences.

Yes, clarifying complex requests with Socratic questioning works effectively for project planning by ensuring mandatory clarification of ambiguous requests. It provides transparent progress reporting and handles errors gracefully to maintain alignment.

A limitation of using a Socratic questioning protocol for decision making is that it mandates clarification before implementation, which may introduce delays for simple tasks. It is specifically designed for complex requirements rather than straightforward modifications.