ask-questions-if-underspecified

To clarify underspecified software requirements, ask targeted questions to define project objectives, acceptance criteria, scope, and constraints. This requirement clarification process prevents wasted development effort by ensuring all necessary details are understood before writing code.

Requirement scoping is the process of defining boundaries, acceptance criteria, and constraints for a development task. You need it when user requests are underspecified, ensuring clarity on environment, safety, and reversibility before implementation begins.

Gather acceptance criteria by asking targeted questions about the user request's expected outcomes, constraints, and scope. Defining these criteria before implementation ensures the final software deliverable meets the defined success conditions.

Ask questions targeting objectives, specific functional requirements, environmental factors, and operational limits. Defining scope and constraints before implementation ensures the development effort aligns with safety requirements and reversibility expectations.

Yes, requirement clarification applies to any software engineering workflow where requests are underspecified. It helps define objectives and constraints across diverse development environments without requiring specific dependencies or platform prerequisites.

Starting implementation without requirement clarification leads to incorrect outputs because objectives, scope, and constraints remain ambiguous. Clarifying these underspecified elements beforehand prevents wasted effort and ensures the code matches actual user expectations.