skills.rest
MrGKanev
MrGKanevCOMMUNITY
Explore all skills by this author →
Website𝕏@mrgkanevGitHub

ask-questions-if-underspecified

Prompt targeted clarifying questions for underspecified requests.

Updated Jan 13, 2026
Search Tags:#workflow#requirements#discovery#questioning#clarifications#underspecified
One-click install
npx skills add https://github.com/MrGKanev/agent-skills --skill ask-questions-if-underspecified-mrgkanev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/MrGKanev/agent-skills/tree/main/my-skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/MrGKanev/agent-skills --skill ask-questions-if-underspecified-mrgkanev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid wrong work by prompting for targeted clarifying questions when a request is underspecified.

Core Features & Use Cases

  • Structured discovery: guides users to identify objective, scope, constraints, and environment before work begins.
  • Minimal questioning: prioritizes 1-5 must-have questions to unlock progress quickly.
  • Workflow templates: provides recommended defaults and response formats to reduce back-and-forth.
  • Use Cases: In a product brief with vague requirements, the Skill generates a compact question set to elicit essential details.

Quick Start

Start by invoking the skill when requirements are vague. It will present a concise set of must-have questions and offer a default path for proceeding with assumptions.

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

Clarifying underspecified requirements involves generating a compact set of one to five must-have questions targeting objective, scope, and success criteria. This structured discovery workflow prompts targeted clarifications to unlock progress quickly before work begins.

What is the best way to request clarifications for a vague feature brief?▼

The best way to request clarifications for a vague feature brief is to apply a minimal questioning workflow that prioritizes essential details. This approach produces a compact, actionable question set to elicit missing information without excessive back-and-forth.

How do I proceed with assumptions when requirements discovery yields no answers?▼

To proceed with assumptions when requirements discovery yields no answers, follow a default workflow path that supplies recommended defaults and response formats. This allows work to continue on underspecified requests without waiting for explicit clarifications.

Does a structured discovery workflow work for incomplete design tasks?▼

Yes, a structured discovery workflow works for incomplete design tasks by applying targeted clarifying questions. It helps determine the environment, success criteria, and objective, ensuring the design scope is fully understood before execution.

How many clarifying questions should I ask for an underspecified project request?▼

You should ask a minimal set of one to five must-have clarifying questions for an underspecified project request. This concise workflow prioritizes essential details to unlock progress quickly rather than overwhelming stakeholders with excessive questioning.

Related Skills

Explore More Product & Management Skills→
BindBind
5

ask-questions-if-underspecified

Prompt must-have questions and pause until user confirms task requirements.

Community
Basic
Ahnd6474Ahnd6474

ask-questions-if-underspecified

Prompt users with clarifying questions before starting ambiguous work.

Community
Basic
darkroomengineeringdarkroomengineering
41

discovery

Guide structured interviews to define project scope and requirements.

Official
Intermediate
onmaxonmax

write-a-prd

Create Product Requirements Documents and generate issues in Linear or GitHub.

Community
Intermediate