brainstorming

To clarify ambiguous requirements, enforce a Socratic questioning protocol that stops implementation and asks at least three decision-revealing questions about purpose, users, and must-have versus nice-to-have features. This prevents building the wrong thing when requests are vague.

Socratic questioning for scope control is a structured protocol that generates consequence-driven questions tied to architectural, cost, complexity, and timeline impacts. It enforces a decision gate requiring explicit answers about purpose and user impact before development begins.

Prevent premature implementation by applying a Socratic gate that prompts minimum three P0/P1/P2 decision-revealing questions before work starts. This structured requirements clarification process stops scope drift and reduces timeline ambiguity.

Yes, structured Socratic questioning applies to feature creation, updates, architecture decisions, and refactoring workflows. It enforces consequence-driven P0/P1/P2 decision questioning to control cost and complexity across new work and existing code changes.

Handle error reporting and progress updates using built-in operational communication protocols that provide consistent error-handling guidance and structured progress reporting patterns. This keeps collaboration transparent and actionable throughout the clarification workflow.

Avoid using Socratic questioning for decision making when requirements are already fully specified and unambiguous, as the consequence-driven questioning protocol is designed specifically to reduce ambiguity and control complexity in complex or vague development requests.