ask-questions-if-underspecified

Generate 1-5 targeted clarifying questions for underspecified requests.

1|Updated Feb 22, 2026

Search Tags:#discovery #decision-making #questioning #requirements-gathering #clarify-underspecification #prompting-strategy #default-paths

Ready to run

npx skills add https://github.com/1337hero/claude-toolkit --skill ask-questions-if-underspecified-1337hero

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/1337hero/claude-toolkit/tree/main/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/1337hero/claude-toolkit --skill ask-questions-if-underspecified-1337hero

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams prevent wasted effort by ensuring requests are fully specified before work begins.

Core Features & Use Cases

Ask must-have questions (1-5) to remove ambiguity and keep work scoped to essential details.
Pause before acting until essential information is gathered to avoid rework.
Fast-path defaults provide safe, initial directions when preferences are assumed, reducing back-and-forth.

Quick Start

Ask the user 1-5 must-have questions to clarify an underspecified request and await 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 a project?▼

Clarifying underspecified requirements involves asking 1-5 must-have questions to remove ambiguity before implementation. This ensures objectives, scope, and constraints are fully defined to prevent wasted effort and rework.

What is requirements gathering and when should I use clarifying questions?▼

Requirements gathering is the process of defining objectives, scope, and constraints. Use clarifying questions when a request is underspecified and has multiple plausible interpretations, ensuring safe execution before action.

How do I prevent wasted effort from ambiguous project requests?▼

Prevent wasted effort by applying a pause before action on ambiguous requests. Use fast-path defaults to provide safe initial directions, reducing back-and-forth while keeping work scoped to essential details.

What is a prompting strategy for decision-making with incomplete information?▼

A prompting strategy for decision-making with incomplete information uses structured questioning to identify must-have details. It applies fast-path defaults when preferences are assumed, allowing safe progression despite missing constraints.

Can I use default paths to skip the discovery phase for simple tasks?▼

Yes, you can use fast-path defaults to skip extensive discovery for simple tasks. These defaults provide safe, initial directions when preferences are assumed, reducing back-and-forth while maintaining essential scoping.

What are the limitations of using automated questioning for scope clarification?▼

The limitation of questioning for scope clarification is that it pauses work until answers are provided. If objectives or environment details remain unaddressed, the fast-path defaults may not fully capture complex constraints.