ask-questions-if-underspecified

Ask targeted questions to clarify underspecified user requests before starting work.

5|Updated Oct 22, 2025

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

Ready to run

npx skills add https://github.com/marchatton/agent-skills --skill ask-questions-if-underspecified-marchatton

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/marchatton/agent-skills/tree/main/.agents/skills/00-utilities/ask-questions-if-underspecified
Command: npx skills add https://github.com/marchatton/agent-skills --skill ask-questions-if-underspecified-marchatton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents wasted effort by ensuring all necessary requirements and constraints are understood before starting a task, reducing the risk of incorrect implementation.

Core Features & Use Cases

Requirement Clarification: Identifies underspecified requests and prompts the user for essential details.
Frictionless Questioning: Asks targeted, easy-to-answer questions with suggested defaults and clear response formats.
Use Case: When asked to "update the user profile page," this Skill will ask clarifying questions about which fields to update, design constraints, and compatibility requirements before proceeding.

Quick Start

Use the ask-questions-if-underspecified skill to clarify the requirements for updating the user profile page.

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 software requirements before starting implementation?▼

To clarify underspecified software requirements, you can use a skill that prompts the user with targeted questions to define objectives, acceptance criteria, scope, and constraints. This prevents incorrect implementation by ensuring all details are understood before coding.

What is the best way to gather project scope and constraints when a user request is ambiguous?▼

The best way to gather project scope and constraints from an ambiguous request is by asking frictionless, targeted questions with suggested defaults. This approach minimizes ambiguity by offering structured choices for environment details and acceptance criteria.

How do I prevent wasted development effort from incorrect task implementations?▼

Prevent wasted development effort from incorrect task implementations by clarifying the request before commencing work. Identifying missing scope and environment details upfront ensures all necessary constraints are understood and met.

Can I use structured questions to define acceptance criteria for an underspecified request?▼

Yes, you can define acceptance criteria for an underspecified request by prompting the user with structured questions. Offering clear response formats and default options helps efficiently gather the exact details needed to prevent incorrect implementations.

When do I need to ask clarifying questions for a software engineering workflow?▼

You need to ask clarifying questions for a software engineering workflow when a user request lacks specific objectives, scope, or environment details. Prompting for these essential constraints before commencing work reduces the risk of building the wrong solution.

Why does asking targeted questions with defaults help with requirement scoping?▼

Asking targeted questions with defaults helps with requirement scoping because it provides a frictionless way for users to define constraints. Suggested answers minimize the effort needed to respond while ensuring the gathered details are accurate enough to proceed.