brainstorming

To clarify vague software requirements, generate targeted questions about goals, users, and constraints before writing code. This discovery process prevents wasted effort on ambiguous requests by forcing clear communication and uncovering missing context.

Investigating complex bugs without assumptions requires Socratic questioning to uncover missing context. By asking at least three high-leverage questions about the bug's scope and impact, you frame trade-offs and avoid premature execution on incorrect recovery paths.

Frame architectural trade-offs for a greenfield feature by applying dynamic question generation to reveal hidden dependencies. This method produces context-aware questions that expose implementation choices and constraints, ensuring you understand the consequences before building.

You need requirement discovery for a code refactor when implementation choices depend on missing context. If the refactor scope is ambiguous or risky, asking structured clarifying questions beforehand prevents architectural assumptions and ensures the refactored solution fits user needs.

Handle blocked progress during requirement discovery by providing structured status updates and defining clear recovery paths. This disciplined progress reporting ensures that when work fails or hits missing context, the communication remains transparent and actionable.