ask-questions-if-underspecified

To clarify requirements, surface 1–5 prioritized questions early in the discovery process and pause for user confirmation. This structured workflow prevents wrong work by surfacing constraints and setting boundaries before any implementation begins.

Underspecified project scope leads to wrong work because unstated constraints and missing stakeholder inputs cause misinterpretation. Clarifying requirements before acting establishes boundaries and ensures implementation matches actual stakeholder discovery needs.

The best way to handle an underspecified request is implementing a structured discovery workflow that surfaces 1–5 prioritized questions, pauses for confirmation, and provides clear fallback behavior before beginning project implementation.

You should ask 1–5 prioritized clarifying questions during project discovery. This minimum set targets underspecified constraints directly, preventing scope creep while respecting stakeholder time before implementation begins.

You should pause to confirm interpretation immediately after surfacing clarifying questions and before any implementation starts. This prevents scope creep and ensures your understanding of constraints aligns with stakeholder requirements.

Yes, you can use a structured questioning workflow in any project phase when requests are underspecified. It surfaces must-have questions and sets boundaries regardless of the development stage to prevent wrong work.