ask-questions-if-underspecified

Ask targeted questions with options and defaults to clarify underspecified requests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/monmacllcapp/skill-forks --skill ask-questions-if-underspecified-monmacllcapp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/monmacllcapp/skill-forks/tree/main/skills/security/plugins/ask-questions-if-underspecified/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/monmacllcapp/skill-forks --skill ask-questions-if-underspecified-monmacllcapp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents wasted effort by ensuring that requirements are clear and unambiguous before implementation begins, especially when a request has multiple plausible interpretations or critical details are missing.

Core Features & Use Cases

  • Requirement Clarification: Identifies and asks targeted questions to resolve underspecified requests.
  • Frictionless Questioning: Uses concise, scannable questions, often with multiple-choice options and suggested defaults, to speed up clarification.
  • Use Case: When asked to "improve the user login flow," this skill would ask clarifying questions about the desired improvements (e.g., security, user experience, performance), scope, and acceptance criteria before proceeding.

Quick Start

Use the ask-questions-if-underspecified skill to clarify the requirements for the task.

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?

You clarify underspecified requirements by asking targeted questions to resolve ambiguity in objectives, scope, constraints, or environment details before implementation begins. This prevents wasted effort by ensuring requests are unambiguous.

Why does my workflow fail when user requests have multiple plausible interpretations?

Your workflow fails because critical details are missing, leading to incorrect assumptions. Using structured questioning with multiple-choice options and suggested defaults resolves this ambiguity efficiently before any implementation work starts.

What is the best way to ask clarifying questions for vague software engineering tasks?

The best way to ask clarifying questions is to use concise, scannable formats with multiple-choice options and suggested defaults. This frictionless questioning approach speeds up requirement gathering when objectives and scope are unclear.

Can I use structured questioning to resolve ambiguity in project scope and constraints?

Yes, you can use structured questioning to resolve ambiguity in project scope and constraints. This approach identifies missing environment details and acceptance criteria, ensuring efficient clarification through targeted questions with defaults.

When do I need requirement clarification in my development workflow?

You need requirement clarification when a request has multiple plausible interpretations or critical details are missing. Asking targeted questions before proceeding ensures objectives, scope, and environment constraints are fully resolved.