moonshot-detect-uncertainty

Detects missing requirements and generates clarification questions. Use after classification/complexity to decide if user input is needed.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026⬇️1downloads

When & Why to Use This Skill

The moonshot-detect-uncertainty skill is a specialized requirement analysis tool designed to identify ambiguities and missing information in user requests. By proactively detecting gaps in UI specifications, API schemas, data ranges, and error-handling policies, it ensures AI agents operate with full context, significantly reducing project misalignment and execution errors.

Use Cases

  • Technical Requirement Scoping: Automatically scanning feature requests to identify missing API endpoints, request/response schemas, or authentication details before development begins.
  • UI/UX Design Clarification: Detecting vague UI requests and prompting users for specific design versions or screen contexts to ensure visual consistency.
  • Data Analysis Precision: Identifying missing parameters in reporting tasks, such as specific date ranges or pagination requirements for large datasets.
  • Agentic Workflow Guardrails: Serving as a logic gate in automated workflows to pause execution and request human intervention when high-priority information is missing.
namemoonshot-detect-uncertainty
descriptionDetects missing requirements and generates clarification questions. Use after classification/complexity to decide if user input is needed.
contextfork

PM Uncertainty Detection

Inputs

  • analysisContext.request.userMessage
  • analysisContext.request.keywords
  • analysisContext.request.taskType
  • analysisContext.signals.hasContextMd

Triggers and questions

  • UI/version: if UI/screen keywords exist, confirm design spec version
  • API: if API keyword exists, confirm endpoint, request/response schema, error format
  • Date range: if date/period keywords exist, confirm single vs range
  • Paging: if list/table keywords exist, confirm server vs client paging
  • Error handling: for new features, confirm alert/toast/inline policy

Output (patch)

missingInfo:
  - category: api-spec
    priority: HIGH
    question: "Please share the API endpoint, request/response schema, and error format."
    reason: "A stable contract is required for mock and type definitions."
signals.hasPendingQuestions: true