ask-questions-if-underspecified

To request clarification for an underspecified work request, you can use a skill that prompts for critical information and requires explicit answers to predefined questions. This validates request completeness before proceeding with implementation.

The best way to avoid making assumptions during a work request is to perform preliminary validation. Asking critical questions ensures all necessary details are provided, minimizing the risk of executing incorrect work.

Question asking before implementation minimizes project risk by ensuring clarity and completeness. By prompting for essential information and requiring explicit answers, it prevents the execution of incorrect work based on missing details.

Yes, you can use preliminary validation to ensure completeness in software engineering tasks. It provides workflow guidance through a structured approach to question-asking, verifying that all necessary details are provided before implementation.

You need to initiate a clarifying session for a work request when the provided details are underspecified. This structured validation step prompts for essential information to prevent incorrect work execution.

The limitation of using predefined questions for request clarification is that it requires explicit answers to a fixed set of queries. This means it strictly validates only against those specific predefined questions before proceeding.