brainstorming

To clarify vague software requirements, enforce a Socratic questioning protocol that surfaces scope, purpose, and constraints before implementation. The skill applies dynamic question generation and mandatory three-question gates to prevent premature design decisions.

Managing project risks during agile brainstorming involves generating context-aware questions that reveal architectural trade-offs. The skill implements structured progress reporting and mandatory questioning gates to surface risks before coding begins.

Preventing premature coding decisions requires a Socratic gate that enforces mandatory questioning for complex requests. The skill triggers at least three clarifying questions to define purpose, users, and scope before proposing a scoped plan.

Yes, Socratic questioning works for poorly defined feature requests by applying dynamic question generation and structured progress reporting. The skill poses context-aware questions to define purpose, users, and scope, then proposes an actionable plan.

Handling error recovery when requirement clarification stalls involves using robust recovery prompts and transparent status updates. The skill provides actionable next steps and structured progress reporting to keep conversations concise and iterative.