ask-questions-if-underspecified

Identify underspecified requests and pose targeted clarifying questions.

1|Updated Jan 31, 2026

Search Tags:#workflow #requirements #clarification #questioning #underspecified

Ready to run

npx skills add https://github.com/allanninal/claude-code-skills --skill ask-questions-if-underspecified-allanninal

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted effort by ensuring that requirements are clear and unambiguous before implementation begins, reducing the risk of misinterpretation and rework.

Core Features & Use Cases

Requirement Clarification: Identifies and asks targeted questions when a request is underspecified.
Frictionless Interaction: Offers multiple-choice options, defaults, and fast-path responses to make clarification easy.
Use Case: When asked to "improve the login flow," this skill would ask clarifying questions about security requirements, user experience goals, and specific areas of the flow to be addressed, rather than making assumptions.

Quick Start

Use the ask-questions-if-underspecified skill to clarify the requirements for the task.

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 coding?▼

Clarifying underspecified requirements before coding involves identifying ambiguities in objectives, scope, and constraints, then posing targeted questions with suggested defaults and multiple-choice options to ensure correct implementation.

What is the best way to prevent wasted effort from ambiguous project requests?▼

Preventing wasted effort from ambiguous project requests requires structured requirement clarification that identifies underspecified requests and asks targeted questions, reducing the risk of misinterpretation and subsequent rework.

How do I ask clarifying questions for a software engineering workflow without slowing down progress?▼

Asking clarifying questions for a software engineering workflow without slowing down requires offering fast-path responses, multiple-choice options, and defaults to make requirement clarification frictionless and easy to resolve.

When do I need to question underspecified objectives in a project?▼

You need to question underspecified objectives in a project when ambiguity in objectives, scope, constraints, or environment could lead to incorrect implementation and cause significant misinterpretation or rework.

How do I handle a vague request like improving a login flow?▼

Handling a vague request like improving a login flow requires asking structured clarifying questions about specific areas, security requirements, and user experience goals, rather than making assumptions about the implementation.