ask-questions-if-underspecified

Ask 1-5 must-have clarifying questions and pause for answers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/petebarbosa/dotfiles --skill ask-questions-if-underspecified-petebarbosa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/petebarbosa/dotfiles/tree/main/opencode/skill/ask-question-if-underspecified
Command: npx skills add https://github.com/petebarbosa/dotfiles --skill ask-questions-if-underspecified-petebarbosa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify when a user request is underspecified by prompting for essential details before proceeding, reducing rework and misinterpretation.

Core Features & Use Cases

  • Guides the user to provide 1-5 must-have clarifying questions to resolve ambiguity.
  • Pauses execution until user responses are provided to avoid proceeding with assumptions.
  • Uses a structured question format with clear recommended defaults to streamline discovery.

Quick Start

Ask the user 1-5 must-have clarifying questions and pause for answers before proceeding.

Frequently Asked Questions about ask-questions-if-underspecified

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify underspecified requirements before starting workflow discovery?

To clarify underspecified requirements, prompt the user with 1-5 must-have clarifying questions about objective, scope, constraints, environment, or safety. Present structured choices with recommended defaults and pause execution until the user provides answers to resolve ambiguity.

What happens when an AI assistant pauses execution after asking clarifying questions?

When an AI assistant pauses execution, it stops processing the request and waits for the user to supply missing key details. This prevents proceeding with assumptions, reducing rework and misinterpretation caused by multiple plausible interpretations of the initial prompt.

When should I prompt for essential clarifications during requirements discovery?

Prompt for essential clarifications when a user request has multiple plausible interpretations or is missing key details about objective, scope, constraints, environment, or safety. This ensures the workflow begins with fully specified requirements rather than guesses.

Can I use structured choices to resolve ambiguous user requests?

Yes, you can use structured choices with clear recommended defaults to streamline discovery when resolving ambiguous user requests. This guides the user to provide essential details quickly and reduces the friction of answering open-ended clarifying questions.

How many must-have clarifying questions should I ask for an underspecified request?

Ask 1-5 must-have clarifying questions to resolve an underspecified request. Limiting the scope to essential questions prevents overwhelming the user while ensuring you gather enough key details about objective, scope, and constraints to proceed safely.

What are the limitations of pausing execution to resolve missing key details?

The limitation of pausing execution is that the workflow cannot proceed until the user responds to the clarifying questions. If the user abandons the session, the process stalls, making it unsuitable for fully autonomous or background processing pipelines.