ask-questions-if-underspecified

To clarify underspecified requirements, this workflow asks 1-5 targeted must-have questions upfront. It pauses all implementation until you provide answers, ensuring objectives and scope are confirmed before any work begins.

The best way to prevent wrong work from ambiguous requests is using a must-have-question workflow. It surfaces essential questions early and forces a pause until acceptance criteria and constraints are clearly resolved.

To ensure a pause for user input when scope is unclear, this workflow intercepts underspecified requests and asks compact, scannable questions. It strictly prevents running commands or editing files until must-have answers arrive.

Yes, you can apply default choices by replying 'defaults'. This fast-path response accepts recommended choices and clears fallbacks, allowing the workflow to confirm interpretation and proceed with implementation.

Yes, this requirements clarification workflow confirms interpretation before acting. After receiving your answers, it provides a concise restatement of the objectives to verify accuracy before proceeding with implementation.

Use a must-have-question workflow for product management tasks whenever objectives, acceptance criteria, scope, constraints, or environment are unclear. It resolves ambiguity early to prevent misinterpretation and wasted effort.