skills.rest
zby
zbyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ask-questions-if-underspecified

Clarify underspecified requests by asking targeted questions about objectives and constraints.

20|5|Updated Nov 18, 2025
Search Tags:#workflow#development#requirements#clarification#questioning#underspecified
One-click install
npx skills add https://github.com/zby/llm-do --skill ask-questions-if-underspecified-zby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/zby/llm-do/tree/main/arscontexta/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/zby/llm-do --skill ask-questions-if-underspecified-zby

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 implementation, reducing the risk of rework and misinterpretation.

Core Features & Use Cases

  • Requirement Clarification: Identifies underspecified requests and prompts the user for essential details.
  • Frictionless Questioning: Presents questions in an easy-to-answer format, including multiple-choice options and suggested defaults.
  • Use Case: When asked to "improve the login page," this Skill will ask clarifying questions about desired UI changes, performance targets, and browser compatibility before proceeding.

Quick Start

Use the ask-questions-if-underspecified skill to clarify the requirements for the new feature request.

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

To clarify underspecified requirements, ask targeted questions about objectives, acceptance criteria, scope, and constraints to prevent wasted effort. This approach pauses execution until essential information is provided or assumptions are confirmed.

What is the best way to stop wasted development effort from misinterpreted feature requests?▼

The best way to stop wasted development effort is to use structured requirement clarification that prompts users for essential details before implementation begins. This reduces the risk of rework by ensuring all necessary constraints are understood.

How does iterative development questioning work for vague user requests?▼

Iterative development questioning works by pausing execution when a request is underspecified and presenting structured questions with multiple-choice options and default suggestions. This ensures essential information is provided before proceeding.

Can I use structured questioning to define acceptance criteria and project scope?▼

Yes, you can use structured questioning to define acceptance criteria, objectives, scope, and constraints. It identifies underspecified requests and prompts the user for essential details using multiple-choice options and suggested defaults.

What are the limitations of pausing execution to ask clarifying questions?▼

A limitation of pausing execution to ask clarifying questions is that it introduces friction before implementation starts. However, this pause is necessary to prevent rework by ensuring all necessary requirements and constraints are understood beforehand.

Related Skills

Explore More Software Engineering Skills→
BAIZ1DBAIZ1D

ralph

Convert unstructured markdown or text PRDs into structured prd.json format.

Community
Intermediate
chf3198chf3198

role-manager-execution

Enforce ticket-first governance and formal handoffs for GitHub work items.

Community
Advanced
FrantssFrantss

wayfinder

Coordinate multi-session project execution through a shared issue-tracker ticket map.

Community
Advanced
yusaduymazyusaduymaz

gsd-spec-phase

Clarify phase requirements through iterative interviews and ambiguity scoring.

Community
Advanced