ask-questions-if-underspecified

Name: ask-questions-if-underspecified
Availability: InStock
Author: Smartfrog

Ask 1-5 essential clarifying questions before starting ambiguous work.

103|9|Updated Jan 3, 2026

Search Tags:#workflow #requirements #clarification #ai-assistant #questioning

Ready to run

npx skills add https://github.com/smartfrog/opencode-froggy --skill ask-questions-if-underspecified-smartfrog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/smartfrog/opencode-froggy/tree/main/skill/ask-questions-if-underspecified
Command: npx skills add https://github.com/smartfrog/opencode-froggy --skill ask-questions-if-underspecified-smartfrog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The workflow helps teams avoid wrong work by guiding the user to surface and resolve ambiguity through a minimal set of must-have questions before starting implementation.

Core Features & Use Cases

Must-have questions first: prompts 1-5 essential questions to surface ambiguity at the outset.
Structured decision flow: uses a formal "question tool" with multiple-choice options to prune interpretations quickly.
Pause and confirm: pauses execution until user answers and confirmation of interpretation is obtained.
Applicable across domains: suitable for software engineering, product design, and research planning where requirements are unclear.

Quick Start

Ask 1-5 must-have questions to clarify user intent before starting any implementation.

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 ambiguous requirements before starting software implementation?▼

To clarify ambiguous requirements before implementation, you can use a must-have-question workflow that prompts 1-5 essential questions to surface ambiguity and pauses execution until interpretations are confirmed.

What is the best way to prevent wrong work from underspecified product design requests?▼

Preventing wrong work from underspecified product design requests involves eliciting essential clarifying questions using a structured decision flow, ensuring objectives and scope are confirmed before concrete work begins.

How does the clarifying question workflow handle unclear project constraints?▼

The clarifying question workflow handles unclear project constraints by using a formal question tool with multiple-choice options to prune interpretations quickly, then pausing for user confirmation of the correct interpretation.

Can I use this requirement clarification process for research planning?▼

Yes, you can use this requirement clarification process for research planning, as it is applicable across domains where objectives, scope, or safety concerns are initially unclear and require structured elicitation.

How many questions should I ask to resolve underspecified requests?▼

You should ask 1-5 must-have questions to resolve underspecified requests, which provides a minimal set to surface core ambiguity at the outset without overwhelming the user before proceeding.

When should I not use a must-have-question workflow for my project?▼

You should not use a must-have-question workflow when your project objectives, scope, and constraints are already fully specified and unambiguous, as the structured questioning process would introduce unnecessary delays.