ask-questions-if-underspecified

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

Identify underspecified project requirements and ask clarifying questions.

1|Updated Apr 7, 2026

Search Tags:#project planning #risk mitigation #requirement clarification #safe task execution #work ambiguity

Ready to run

npx skills add https://github.com/rohanbhatia27/rohanstutoring-redesign --skill ask-questions-if-underspecified-rohanbhatia27

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ask-questions-if-underspecified
Source: https://github.com/rohanbhatia27/rohanstutoring-redesign/tree/main/.agents/skills/ask-questions-if-underspecified
Command: npx skills add https://github.com/rohanbhatia27/rohanstutoring-redesign --skill ask-questions-if-underspecified-rohanbhatia27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures work isn't prematurely implemented, mitigating costly rework due to misunderstanding of project objectives.

Core Features & Use Cases

Risk Reduction: Aids in clarifying ambiguities, thereby avoiding assumptions that lead to misdirection in task execution.
Process Efficiency: Guides a systematic questioning process that expedites accurate interpretation and efficient action planning.
Use Case: Prior to deploying resources to a new software development feature, it assists in validating project goals and acceptance criteria with the requestor, saving valuable time and resources.

Quick Start

Use the "ask-questions-if-underspecified" skill before initiating a new project feature or task. Confirm with: "Before proceeding, are the following elements clear: objectives, 'done' criteria, scope, constraints, and environment?"

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 project requirements before starting development?▼

To reduce costly assumptions in task execution, you must validate project goals and acceptance criteria with the requestor prior to deployment. Confirming elements like objectives, 'done' criteria, scope, and constraints ensures accurate interpretation and prevents costly rework.

What is the best way to mitigate risk when project scope is underspecified?▼

Mitigating risk for underspecified project scope requires a systematic questioning process that expedites accurate interpretation and efficient action planning. By validating project goals and acceptance criteria with the requestor beforehand, you prevent misdirection and ensure accurate, safe task execution.

How do I prevent rework caused by misunderstanding software development objectives?▼

Preventing rework from misunderstood software development objectives requires identifying underspecified requirements and asking essential clarifying questions beforehand. Validating goals, scope, and acceptance criteria with the requestor ensures work isn't prematurely implemented and saves valuable resources.

Does requirement clarification work for technical workflows with safety and reversibility considerations?▼

Requirement clarification works effectively for technical workflows by ensuring accurate and safe task execution with specific considerations for language version, safety, and reversibility. This process identifies underspecified requirements and asks essential clarifying questions tailored for administrative and technical environments.

When should I not proceed with task execution due to work ambiguity?▼

You should not proceed with task execution when elements like objectives, 'done' criteria, scope, constraints, and environment are unclear. Halt implementation to ask essential clarifying questions, mitigating the risk of costly rework due to misunderstanding of project objectives.