ask-questions-if-unspecified

Clarify underspecified user requests by asking targeted questions about objectives, scope, constraints, and environment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents wasted effort by ensuring all necessary details are clarified before starting implementation, especially for ambiguous or underspecified requests.

Core Features & Use Cases

  • Requirement Clarification: Identifies and asks targeted questions about scope, objectives, constraints, and environment.
  • Ambiguity Resolution: Handles vague instructions like "fix this" or "improve it" by seeking specific details.
  • Use Case: When asked to "optimize the user profile page," this skill will ask clarifying questions about which specific aspects to optimize (e.g., load time, UI elements, data fetching) and what defines "optimized."

Quick Start

Use the ask-questions-if-unspecified skill to clarify the requirements for updating the user authentication flow.

Frequently Asked Questions about ask-questions-if-unspecified

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

FAQPage Schema
How do I clarify ambiguous software requirements before starting implementation?

Clarifying ambiguous software requirements involves asking targeted questions about objectives, scope, constraints, and environment to resolve underspecified requests. This structured questioning approach ensures alignment and prevents incorrect work before coding begins.

What is the best way to resolve vague workflow instructions like optimize or fix this?

Resolving vague workflow instructions requires identifying missing critical details and asking specific questions about expected outcomes. A structured approach with options for defaults and fast-path responses handles ambiguity by seeking exact parameters for the requested changes.

How do I prevent wasted effort when dealing with underspecified user requests?

Preventing wasted effort from underspecified user requests requires identifying missing critical details and requesting clarification upfront. By asking targeted questions about environment and constraints before proceeding, you ensure alignment and avoid implementing incorrect work.

Can I use a structured questioning approach to define scope for missing project details?

Yes, a structured questioning approach supports scenarios with missing critical details by offering options for defaults and fast-path responses. This method defines project scope by systematically resolving ambiguities in objectives, constraints, and environment before implementation.

When should I ask clarifying questions about constraints and environment instead of assuming defaults?

You should ask clarifying questions about constraints and environment whenever user requests are ambiguous or missing critical details. Requesting targeted clarification before proceeding prevents incorrect work and ensures alignment, even when fast-path default options are available.