skills.rest
Dayopt
DayoptOFFICIAL
Explore all skills by this author →
GitHub

ask-questions-if-underspecified

Ask 1-5 clarifying questions and pause until requirements are specified.

Updated Jun 23, 2025
Search Tags:#workflow#requirements#discovery#clarify#underspecified#question-templates
One-click install
npx skills add https://github.com/Dayopt/app --skill ask-questions-if-underspecified-dayopt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/Dayopt/app/tree/main/.claude/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/Dayopt/app --skill ask-questions-if-underspecified-dayopt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify requirements before implementing. Use when serious doubts araise.

Core Features & Use Cases

  • Provides a structured workflow to identify when a request is underspecified across objective, scope, constraints, environment, and safety.
  • Uses a minimal set of must-have clarifying questions (1-5) to eliminate ambiguity and prevent scope creep.
  • Defines a safe pause protocol to halt implementation until essential answers are provided, reducing rework and misinterpretation.

Quick Start

Ask the minimum set of clarifying questions in the first pass and pause for user answers before proceeding.

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

To clarify underspecified requirements, you identify gaps across objective, scope, constraints, environment, and safety. Ask a minimal set of 1-5 clarifying questions upfront to eliminate ambiguity and prevent scope creep before writing any code.

What is a safe pause protocol for workflow discovery?▼

A safe pause protocol halts implementation entirely until essential answers to clarifying questions are provided. This discovery mechanism prevents rework and misinterpretation by ensuring no work proceeds on ambiguous requirements.

How many clarifying questions should I ask when a request is unclear?▼

You should ask a minimal set of 1 to 5 clarifying questions when a request is unclear. This targeted discovery approach resolves ambiguity across objectives and constraints without overwhelming the requester.

When do I need to pause work on a task due to unclear scope?▼

You need to pause work when serious doubts arise about objectives, scope, constraints, environment, or safety. Stopping implementation immediately prevents rework and ensures all critical ambiguities are resolved before proceeding.

What is the best way to prevent scope creep during requirements discovery?▼

The best way to prevent scope creep is to use structured question-templates to ask must-have clarifying questions first. Pausing implementation until these answers are provided stops misinterpretation and uncontrolled project expansion.

Related Skills

Explore More Product & Management Skills→
mejangomejango

ask-questions-if-underspecified

Prompt essential clarifying questions for underspecified requests.

Community
Basic
stribusstribus
1

reversa-resume

Swap the active feature with one from paused-features in active-requirements.json.

Community
Advanced
nullhacknullhack
11

define-scope

Conduct stakeholder interviews to generate scope journals and .feature descriptions.

Community
Intermediate
NodeJSmithNodeJSmith
1

mine.interviewer

Conduct a structured discovery interview to generate a project specification document.

Community
Intermediate