ask-questions-if-underspecified

Prompt must-have questions and pause until user confirms task requirements.

5|Updated Dec 28, 2025

Search Tags:#workflow #requirements #scope #elicitation #acceptance-criteria #clarify #underspecified

Ready to run

npx skills add https://github.com/Bind/skillz.sh --skill ask-questions-if-underspecified-bind

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/Bind/skillz.sh/tree/main/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/Bind/skillz.sh --skill ask-questions-if-underspecified-bind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid wrong work by ensuring clarifications are gathered before starting implementation.

Core Features & Use Cases

Must-have questions first: Prompt for the essential details needed to proceed.
Scope, objectives, and constraints: Guides users to define success criteria and environment requirements.
Pause and confirm: Pauses work until the user confirms assumptions or proceeds with stated defaults.

Quick Start

Use this Skill to prompt a requester for key clarifications whenever a task is underspecified.

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

To clarify underspecified requirements, prompt the requester for essential details like objective definitions, acceptance criteria, and scope. This prevents wrong work by pausing implementation until the user explicitly confirms assumptions or approves stated defaults.

What questions should I ask to define scope and acceptance criteria for a task?▼

Defining scope and acceptance criteria requires asking must-have questions about success objectives, constraints, environment requirements, and safety checks. Gathering these details upfront ensures the task has objective definition before any implementation work begins.

How do I prevent wrong work when a project request lacks objective definition?▼

Preventing wrong work involves pausing execution when a request lacks objective definition. You must prompt the requester for key clarifications regarding scope and constraints, seeking explicit user confirmation before proceeding with the implementation.

When should I pause execution to gather elicitation details for a workflow?▼

Pause execution to gather elicitation details whenever a workflow task is underspecified and needs objective definition. This pause ensures essential safety checks, environment requirements, and acceptance criteria are confirmed before moving forward with implementation.

Can I proceed with default assumptions if a task scope is underspecified?▼

You can proceed with default assumptions if a task scope is underspecified, but execution must pause until the user provides explicit approval. Prompting for must-have questions first ensures the requester confirms or corrects these defaults to prevent wrong work.