ask-questions-if-underspecified

To clarify ambiguous software requirements, you need to identify missing objective, scope, and acceptance criteria, then collect minimum must-have answers to prevent wasted effort. This ensures correct changes are made by prompting for missing details before implementation begins.

Defining scope for a vague feature request involves asking 1-5 scannable multiple-choice questions to eliminate major interpretation branches. This forces quick alignment on what constitutes 'done' before any code changes or refactors are executed.

Preventing incorrect changes when integration requirements are unclear requires a safe pause before action. You avoid running commands or editing files until key uncertainties regarding data or rollout risk are resolved or assumptions are explicitly approved.

You need to ask clarifying questions for a software refactor when underspecification is detected. If objective, constraints, environment, or safety and reversibility are unclear, asking must-have questions aligns expectations and prevents incorrect changes.

Requirement underspecification detection works by identifying when objective, acceptance criteria, scope, constraints, environment, or safety are unclear. It forces quick alignment on scope before work starts, ensuring missing details are prompted before implementation begins.