ask-questions-if-underspecified

To clarify underspecified requirements, prompt for essential missing details across objectives, scope, constraints, and environment. Ask a minimum set of must-have questions and enforce a pause for user answers before proceeding.

The best way to avoid wrong work from ambiguous requests is to propose clear default assumptions and a fast-path for confirmation. This ensures mutual understanding before implementation begins.

Requirement discovery handles safety gaps by prompting for essential missing details across diverse task domains. It targets objectives, scope, constraints, environment, and safety gaps to prevent misinterpretations.

For workflow discovery, ask one to five must-have clarifying questions and pause for user answers before proceeding. This enforces a minimum set of questions to avoid wasted effort.

You need to enforce a pause for decision-making during requirements gathering whenever a request is underspecified. This pause ensures all must-have answers regarding scope and constraints are provided before acting.

Yes, you can use default assumptions for fast-path confirmation in requirement discovery. Proposing clear defaults allows quick validation of objectives and constraints without lengthy clarification cycles.