ask-questions-if-underspecified

Clarify underspecified requests with 1-5 must-have questions before implementation.

2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/roderik/mpe --skill ask-questions-if-underspecified-roderik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/roderik/mpe/tree/main/.agents/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/roderik/mpe --skill ask-questions-if-underspecified-roderik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify requests that are underspecified before starting work to avoid misaligned outcomes and wasted effort.

Core Features & Use Cases

  • Must-have questions: prompts the minimum set of clarifying questions (1-5) needed to define objective, scope, constraints, and environment.
  • Structured discovery: guides users through a concise, scannable decision path to reach a clear plan.
  • Pause-and-confirm workflow: halts execution until the user provides answers or approves assumptions.

Quick Start

Describe an underspecified request to the agent. The agent will present a compact list of must-have questions and await your confirmation 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 project planning?

Clarifying underspecified requirements involves prompting a minimum set of 1-5 targeted questions to define objectives, scope, and constraints. This structured discovery process pauses execution until you provide answers or approve assumptions, preventing misaligned outcomes.

What is the best way to prevent misaligned outcomes from ambiguous requests?

Preventing misaligned outcomes from ambiguous requests requires a pause-and-confirm workflow that halts execution for explicit confirmation. By guiding users through a concise, scannable decision path, the agent ensures all assumptions are validated before proceeding.

How do I ask targeted clarifying questions for workflow communication?

Asking targeted clarifying questions for workflow communication means identifying gaps in objective, scope, constraints, environment, or safety. The agent generates a compact list of must-have questions and awaits your confirmation before moving forward.

Can I use a fast-path for defaults when clarifying ambiguous objectives?

Yes, you can use a fast-path for defaults when clarifying ambiguous objectives. If you prefer not to answer all 1-5 must-have questions, the workflow provides a quick start path that allows you to approve assumptions and proceed immediately.

When do I need to pause execution for scope and constraint confirmation?

You need to pause execution for scope and constraint confirmation whenever a request is underspecified. The pause-and-confirm workflow halts all actions until you explicitly answer the required questions or approve the default assumptions provided.

Why does my agent start implementation without asking clarifying questions?

Agents start implementation without asking clarifying questions when no structured discovery workflow is enforced. Applying a must-have questions prompt ensures the agent always pauses to collect explicit confirmation on objectives and scope before beginning work.