ask-questions-if-underspecified

Generates targeted clarifying questions before implementing ambiguous user requests.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill ask-questions-if-underspecified-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill ask-questions-if-underspecified-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague or ambiguous requests often lead AI agents to build the wrong thing, wasting effort on rework. This Skill ensures the agent pauses to clarify objectives, scope, constraints, and acceptance criteria before writing any code. ## Core Features & Use Cases - Underspecification Detection: Evaluates requests against a checklist covering objective, definition of done, scope, constraints, environment, and safety to decide whether clarification is needed. - Structured Question Format: Produces 1-5 numbered, multiple-choice questions with recommended defaults, fast-path replies (e.g., "defaults"), and compact answer formats like "1a 2b". - Safe Pause Behavior: Blocks edits, commands, and detailed planning until must-have answers arrive, while permitting clearly labeled low-risk discovery reads. - Use Case: A user asks to "improve the API." Instead of guessing, the agent asks which endpoints are in scope, what performance target defines success, and whether backward compatibility is required, then confirms the interpretation before coding. ## Quick Start Ask the agent to review my request for ambiguity and ask clarifying questions before making any changes.

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 get an AI agent to ask clarifying questions before coding?

Instruct the agent to treat requests with unclear objectives, scope, or constraints as underspecified and ask 1-5 numbered questions first. This Skill enforces that behavior, blocking edits and commands until must-have answers arrive.

What makes a good clarifying question for AI agents?

Good clarifying questions are short, numbered, and offer multiple-choice options with a bolded recommended default. They eliminate whole branches of work and support compact replies like "1a 2b" or a single "defaults" fast-path response.

When should an AI agent not ask clarifying questions?

Skip questions when the request is already clear or when a quick, low-risk discovery read of configs, existing patterns, or docs can answer the gap. Asking about easily discoverable facts adds friction without value.

What happens if the user tells the agent to proceed without answering?

The agent states its assumptions as a short numbered list and asks for explicit confirmation. It only proceeds after the user confirms or corrects those assumptions, keeping the user in control of ambiguous decisions.

How many clarifying questions should be asked at once?

Ask 1-5 questions in the first pass, prioritizing must-have questions that eliminate entire branches of work. Separate "need to know" from "nice to know" items to reduce friction and speed up the user's response.