ask-questions-if-underspecified

Clarifying requirements before implementation involves identifying missing objectives, constraints, or environment details, then prompting concise must-have questions. This prevents incorrect outcomes by ensuring scope is fully defined before any work begins.

You should use a plan mode when evaluating scope or risk reveals multiple subsystems, high risk, or unclear effort. It proposes a concise planning step to define the work structure before execution, pausing until you provide explicit confirmation to proceed safely.

The best way to prevent incorrect work from ambiguous requests is to target undetermined aspects across scope, constraints, and environment. By pausing to ask must-have questions and awaiting explicit confirmation, you enforce safe, stepwise execution before proceeding.

You ensure safe stepwise execution by reading the relevant documentation first, identifying missing constraints, and pausing work for user answers. You proceed only after receiving explicit confirmation or agreeing on given defaults for the requirements.

Yes, clarifying requirements works for complex environments. When multiple subsystems or high risk are detected, it automatically suggests a planning step to evaluate scope, ensuring safe progression by pausing for explicit user confirmation before implementation.