ask-questions-if-underspecified

To clarify vague requirements, this skill identifies missing scope, constraints, and objectives, then generates a concise set of 1-5 must-have questions with sensible defaults to accelerate alignment.

You need to pause task execution for requirements gathering when a request is underspecified and multiple interpretations exist, continuing only after essential questions are answered or assumptions are approved.

The best way to disambiguate user prompts during task scoping is to pinpoint missing environment and safety details, then prompt the user with a minimal set of must-have questions to resolve the ambiguity.

You identify if a request lacks enough detail by evaluating it for missing objectives, scope, constraints, and environment details, which reduces the risk of misinterpretation and rework.

Yes, you can use this approach to reduce rework caused by misinterpreted instructions by enforcing a disciplined method that guides users to supply essential information through focused clarifying questions.

If a user approves assumptions instead of answering clarifying questions, the skill stops pausing execution and proceeds with the confirmed interpretation to complete the underspecified task.