moonshot-detect-uncertainty

To identify missing requirements, the system analyzes task classification and complexity to find incomplete information. It then generates targeted clarification questions to resolve gaps across UI, API, date-range, paging, and error-handling contexts before work proceeds.

Clarification questions are targeted prompts used when task information is incomplete. You need them after classifying task complexity to determine whether user input is required to resolve ambiguity before proceeding with development.

Generating clarification questions involves computing where information is incomplete after assessing task complexity. It produces specific questions to gate user prompts based on task type, ensuring stakeholders provide necessary input for UI, API, and error-handling scenarios.

Yes, the requirements analysis applies to UI, API, date-range, paging, and error-handling scenarios. It evaluates whether user input is needed across these specific contexts to reduce project ambiguity.

The best way to reduce ambiguity is to detect missing requirements early and generate context-aware clarification questions. This gates user prompts based on task type and ensures consistent prompting before development begins.

You should not use automated clarification generation before completing task classification and complexity analysis. It is designed to run after these steps to accurately determine whether user input is still required.