ask-questions-if-underspecified

To clarify underspecified software development requests, use a skill that asks targeted questions about objectives, scope, constraints, and environment. This ensures requirements are fully gathered and understood before any implementation begins.

Asking clarifying questions before writing code prevents wasted effort and incorrect implementations. Ensuring all necessary details are clear early in the process helps avoid errors and rework during software development.

The best way to define project scope for a vague task is to facilitate requirement gathering by asking targeted questions about specific constraints and environments. This approach ensures clarity on objectives before starting the work.

To gather requirements for a website improvement task, prompt the user with clarifying questions about which pages require changes, what kind of improvements are needed, and whether there are specific performance targets to meet.

Yes, you can use this requirement clarification approach for any software engineering task where the request is underspecified. It helps define the environment and constraints to ensure clarity across diverse development scenarios.

If you start coding without clarifying constraints, you risk wasted effort and incorrect implementations. Clarifying objectives and environment details beforehand is necessary to prevent errors and rework.