ask-questions-if-underspecified

Generates minimal clarifying questions before drafting requirements, user stories, or PRDs.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/jason23452/my-skill --skill ask-questions-if-underspecified-jason23452
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/jason23452/my-skill/tree/main/flow/ask-questions-if-underspecified
Command: npx skills add https://github.com/jason23452/my-skill --skill ask-questions-if-underspecified-jason23452

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafting requirements, user stories, or PRDs from vague prompts forces risky assumptions about scope, actors, and success criteria. This Skill pauses the workflow and asks only the smallest useful set of clarifying questions before any drafting begins. ## Core Features & Use Cases - Ambiguity Detection: Identifies unclear objectives, actors, scope, constraints, success criteria, acceptance scenarios, and source documents that would materially change the requirement. - Structured Question Plans: Produces a host-agent-compatible questionPlan with 1-7 questions, recommended options marked (Recommended), and copy-ready requirement sentences as option descriptions. - Prompt-Derived Questions: Builds questions from the user's own words by turning nouns into managed objects, verbs into workflows, and quality adjectives into measurable success criteria. - Use Case: A user says "build a customer portal". Before drafting a PRD, the Skill asks about target actors, managed objects, core workflows, lifecycle states, non-goals, and success criteria instead of guessing. ## Quick Start Ask the agent to review my feature request and ask clarifying questions before drafting the requirements document.

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 ask clarifying questions before writing a PRD?▼

Identify which of objective, actor, scope, success criteria, constraints, or acceptance criteria are unclear, then ask only the smallest set of questions whose answers would change the draft. Questions that can be safely recorded as assumptions or non-goals should not be asked.

How many clarifying questions should a requirements gate ask?▼

A normal clarification gate asks 1 to 5 questions. For broad product requests, 4 to 7 questions in one gate are acceptable when fewer would force risky assumptions about outcome, actors, workflows, or success criteria.

When should I not ask clarifying questions in requirements work?▼

Do not ask about implementation details like APIs, databases, frameworks, UI kits, or deployment unless the user made them constraints. Also avoid broad prompts like "any other details?" and do not block drafting when explicit assumptions suffice.

How do I turn a vague product prompt into requirement questions?▼

Derive questions from the user's own words: nouns become candidate managed objects or roles, verbs become workflows, product shape words become scope questions, and quality adjectives become measurable success criteria.

What happens after clarifying questions are answered?▼

The confirmed requirement deltas are restated and the current requirements flow continues. The Skill does not branch into user story writing, PRD drafting, or project-flow stages unless the host agent explicitly owns that stage.