ask-questions-if-underspecified

Clarifying underspecified requirements involves asking targeted questions about objectives, scope, constraints, and environment before acting. This prevents wasted effort and incorrect implementations by ensuring all necessary details are clear.

Scoping a vague request requires identifying missing critical information and using structured prompts to gather details. Suggested defaults and multiple-choice options can minimize ambiguity and facilitate efficient requirement gathering.

Preventing incorrect implementations requires obtaining critical information through concise questions before proceeding. Asking about specific safety considerations and compatibility requirements ensures the correct interpretation is chosen.

Yes, structured prompts can gather project constraints and objectives by offering scannable questions with suggested defaults. This makes answering easy and ensures all essential details are collected efficiently.

You need to ask clarifying questions about workflow scope when a request is underspecified or has multiple interpretations. Gathering these details beforehand prevents wasted effort and ensures the task meets actual objectives.