skills.rest
czer323
czer323COMMUNITY
Explore all skills by this author →
GitHub

ask-questions-if-underspecified

Ask essential questions to clarify underspecified requests before execution.

Updated Aug 2, 2025
Search Tags:#planning#requirements#communication#questions#clarify#underdspecified
One-click install
npx skills add https://github.com/czer323/d3-item-salvager --skill ask-questions-if-underspecified-czer323
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/czer323/d3-item-salvager/tree/main/.claude/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/czer323/d3-item-salvager --skill ask-questions-if-underspecified-czer323

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarifies underspecified requests by prompting for essential information before acting, reducing misinterpretation and rework.

Core Features & Use Cases

  • Interrogates ambiguous requests to identify missing objective, scope, constraints, acceptance criteria, and environment.
  • Generates a concise set of must-have questions to collect the needed details.
  • Safeguards project timelines by preventing premature execution when requirements are unclear.
  • Use Case: In product planning, when requirements are vague, the skill asks targeted questions to reach a shared definition.

Quick Start

Ask the user 1-5 must-have questions to clarify the request 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 requirements before starting a project with vague requests?▼

To clarify requirements before starting a project, prompt essential questions covering objectives, acceptance criteria, constraints, and environment. This prevents premature execution and reduces misinterpretation by guiding users to provide critical missing details.

What is the best way to collect missing details for an underspecified feature request?▼

The best way to collect missing details for an underspecified feature request is generating a concise set of one to five must-have questions. This targets ambiguities to identify missing scope, objectives, and constraints to reach a shared definition.

How do I prevent premature execution when project scope is unclear?▼

To prevent premature execution when project scope is unclear, enforce a safety safeguard that interrogates ambiguous requests first. Asking targeted questions before acting avoids rework and ensures timelines are protected from unvalidated assumptions.

Can I use requirement clarification questions for simple tasks or is it only for complex planning?▼

You can use requirement clarification questions across project scopes from simple tasks to complex feature requests. The process scales by adjusting the one to five must-have questions to match the specific planning context and needed details.

Why does my project planning fail when requirements are underspecified?▼

Project planning fails when requirements are underspecified due to misinterpretation and rework caused by missing objective, scope, constraints, and environment details. Prompting essential questions beforehand enforces safety by ensuring a shared definition before action.

Related Skills

Explore More Content & Communication Skills→
OzeroHAXOzeroHAX
32

docs-project-brief

Define project context, problem statement, and MVP boundaries.

Community
Basic
realsigridjinrealsigridjin
20

ralph-init

Create a structured Product Requirements Document from a project description.

Community
Intermediate
SkillPanelSkillPanel
199

docs-manager

Manage project documentation and standards in the .maister/docs/ repository.

Official
Advanced
DevelopersGlobalDevelopersGlobal
65

idea-to-spec

Transform informal project ideas into structured, testable specifications.

Official
Intermediate