ask-questions-if-underspecified

You can detect vague software development requests by applying a structured clarification process that identifies missing objectives, scope boundaries, or constraints. This skill forces explicit confirmation of acceptance criteria before executing any technical changes.

You need to ask clarifying questions for task planning when objectives, constraints, or acceptance criteria are ambiguous. This skill ensures operational safety by requiring explicit confirmation of scope before executing technical changes or code modifications.

The best way to prevent incorrect implementations from vague user requests is to use a structured inquiry framework. This approach identifies missing parameters, such as specific table names or migration requirements, and resolves contradictions before development begins.

Yes, this structured clarification approach works specifically for software development and task planning scenarios. It provides templates for asking concise questions that ensure operational safety and efficiency before executing technical changes.

A limitation of automated questioning for requirements gathering is that it requires the user to actively provide the specific constraints, table names, or safety constraints requested. The framework identifies the ambiguity but cannot generate the missing requirements independently.