skills.rest
ivanov-i
ivanov-iCOMMUNITY
Explore all skills by this author →
GitHub

ask-questions-if-underspecified

Ask must-have questions to clarify requirements before starting work.

Updated Aug 12, 2018
Search Tags:#requirements#scope#acceptance-criteria#questioning#clarify#requirements-gathering#project-clarity
One-click install
npx skills add https://github.com/ivanov-i/dots --skill ask-questions-if-underspecified-ivanov-i
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/ivanov-i/dots/tree/main/codex/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/ivanov-i/dots --skill ask-questions-if-underspecified-ivanov-i

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify requirements before starting work to prevent wrong directions or wasted effort.

Core Features & Use Cases

  • Collects must-have questions early to unlock accurate scope and acceptance criteria.
  • Prevents scope creep by ensuring explicit assumptions are documented before work begins.
  • Applies to project requests, feature requests, and any work where uncertainty exists.

Quick Start

Ask 1-5 must-have questions in the first response and pause until you get clear answers or approved assumptions.

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 project requirements before starting development?▼

To clarify project requirements, ask 1-5 must-have questions early to determine objectives, scope, constraints, environment, and acceptance criteria, pausing until explicit confirmation or approved assumptions are provided.

What is the best way to prevent scope creep when gathering requirements?▼

Preventing scope creep requires documenting explicit assumptions and defining clear acceptance criteria before work begins, ensuring all stakeholders confirm project boundaries and expected outcomes upfront.

How do I define acceptance criteria for uncertain feature requests?▼

Defining acceptance criteria for uncertain feature requests involves asking targeted questions first to unlock accurate scope, ensuring you only proceed after receiving clear answers or explicitly documented and approved assumptions.

Can I use requirements questioning for project requests with minimal initial scope?▼

Yes, requirements questioning applies to project requests, feature requests, and any work where uncertainty exists, helping collect must-have questions early to establish accurate scope and constraints before execution.

Why does starting work without clarifying requirements lead to wasted effort?▼

Starting work without clarifying requirements leads to wasted effort because misaligned outcomes occur when objectives, scope, and constraints are not explicitly confirmed, causing wrong directions and rework.

Related Skills

Explore More Product & Management Skills→
alessioroberto82alessioroberto82

scope

Gather requirements and define project scope for new features.

Community
Intermediate
jpoutrinjpoutrin
14

parallel-prompt-generator

Generate agent-ready prompts from task specification files.

Community
Advanced
jshsakurajshsakura
22

business-analyst

Clarify requirements, normalize scope, and define acceptance criteria from messy inputs.

Community
Intermediate
X-School-AcademyX-School-Academy
9

dev-swarm-mvp

Define MVP scope, success metrics, and acceptance criteria for early product validation.

Official
Basic