ask-questions-if-underspecified

Clarify requirements before starting software development by identifying missing objectives, scope, and constraints, then prompting a concise set of 1-5 questions to resolve ambiguity. This guided discovery ensures a safe pause workflow until necessary details are confirmed.

Gather missing project scope information through a must-have questioning approach that identifies gaps in objectives, constraints, and environment. It pauses progress to capture assumptions for later review until questions are answered or assumptions approved.

Prevent premature implementation when product design details are unclear by applying a safe pause workflow that halts execution. It identifies underspecified requests and prompts essential clarifications before any development action begins.

Yes, you can use structured discovery for software development and project scoping. It identifies underspecified requests by prompting essential clarifications across both domains, ensuring a minimal set of must-have questions before taking action.

Capture assumptions during requirements discovery by recording accepted assumptions for later review. This occurs within a safe pause workflow that holds progress until clarifying questions are answered or the captured assumptions are explicitly approved.

Ask clarifying questions for decision-making when requests are underspecified or incomplete. Prompting essential clarifications before taking action ensures objectives, scope, and safety considerations are fully resolved in product design and project scoping.