ask-questions-if-underspecified

Prompt essential clarifying questions for underspecified requests.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/mejango/juicy-vision --skill ask-questions-if-underspecified-mejango
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/mejango/juicy-vision/tree/main/.claude/plugins/ask-questions-if-underspecified/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/mejango/juicy-vision --skill ask-questions-if-underspecified-mejango

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams avoid misaligned work by prompting for essential clarifications before starting any implementation.

Core Features & Use Cases

  • Must-have questions first: Identifies and requests the minimal set of questions needed to resolve ambiguity.
  • Risk reduction: Reduces rework by clarifying objective, scope, constraints, environment, and safety.
  • Use Case: When a request lacks objective, scope, or constraints, the skill guides the user to provide the necessary details.

Quick Start

Respond when you detect an underspecified request. Provide 1-5 must-have questions in a compact list to clarify: 1) Objective? 2) Scope? 3) Constraints? 4) Environment? 5) Safety considerations?

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 work?

To clarify underspecified requirements, prompt a minimal set of must-have questions covering the objective, scope, constraints, environment, and safety considerations. This ensures essential ambiguities are resolved before implementation begins.

What questions should I ask to reduce risk when project scope is unclear?

To reduce risk when project scope is unclear, ask targeted questions about the objective, scope boundaries, constraints, environment, and safety considerations. Requesting these must-have answers early prevents misaligned work and rework.

Why does development work start without clear objectives and constraints?

Development work starts without clear objectives and constraints when underspecified requests bypass discovery. Prompting essential clarifying questions ensures the minimal must-have information is gathered before work proceeds.

Can I use automated questioning to handle ambiguous feature requests?

Yes, you can use automated questioning to handle ambiguous feature requests by detecting underspecified inputs and automatically prompting 1-5 compact must-have questions about scope, environment, and safety.

What is the best way to do requirements discovery for a new workflow?

The best way to do requirements discovery for a new workflow is prompting a focused list of must-have questions. Clarifying the objective, scope, constraints, and environment minimizes ambiguity and reduces project risk.