ask-questions-if-underspecified

To clarify requirements before implementation, you need to identify underspecified objectives, scope, and constraints. This skill facilitates requirement gathering by asking targeted, scannable questions with multiple-choice options and suggested defaults to ensure clarity.

Scoping underspecified requests involves prompting the user for necessary details about their environment and safety constraints. Structured questioning prevents wasted effort by ensuring requests are unambiguous, reducing the risk of misinterpretation and rework before coding begins.

Gathering project constraints requires asking targeted questions about specific user segments, performance targets, and acceptable trade-offs. This skill identifies underspecified requests and prompts the user for these necessary details to define the exact scope.

Development fails when requirements are underspecified due to misinterpretation and rework. Clarifying the objective, scope, and environment constraints before initiating implementation tasks prevents wasted effort and ensures the final output matches expectations.

Yes, structured questioning defines the scope of workflow optimization by asking clarifying questions about performance targets and acceptable security trade-offs. This approach ensures the objective and constraints are clear before any optimization implementation begins.