ask-questions-if-underspecified

Ask targeted questions to clarify project objectives, scope, and constraints.

5|Updated Jan 14, 2025

Search Tags:#project management #requirements #clarification #decision-making #questioning

Ready to run

npx skills add https://github.com/timmo001/dotfiles --skill ask-questions-if-underspecified-timmo001

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Clarifies ambiguities in project requests to prevent rework, risk, or incorrect outcomes by asking targeted questions only when necessary.

Core Features & Use Cases

Clarification Guidance: Guides users to pinpoint critical unknowns such as objectives, scope, and constraints.
Decision Support: Uses a structured approach to collect minimal, high-impact information through concise, multiple-choice questions.
Use Case: When a developer faces vague feature requests, they employ this skill to ask precise questions, reducing ambiguity and ensuring correct implementation.

Quick Start

Use this skill to identify key ambiguities in your project specifications with minimal questions asking.

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

To clarify vague project requirements, you can use a structured approach to ask targeted, concise questions that pinpoint critical unknowns like objectives, scope, and constraints. This minimizes rework by collecting only high-impact information through multiple-choice questions.

What is the best way to ask clarifying questions about feature scope without overwhelming stakeholders?▼

The best way to ask clarifying questions without overwhelming stakeholders is to ask minimal questions only when ambiguity materially changes implementation. This structured approach focuses on decision support, collecting necessary information efficiently to reduce project risk.

When should I ask clarifying questions during project planning and feature development?▼

You should ask clarifying questions during project planning and feature development when ambiguity materially changes implementation. Identifying critical unknowns early ensures safe, efficient clarification workflows and reduces the risk of incorrect outcomes or rework.

How do I resolve project ambiguities using a structured decision-making process?▼

Resolving project ambiguities requires identifying critical unknowns and using a structured decision-making process to record answers. By asking concise, targeted questions, you reduce implementation risk and ensure correct feature development outcomes.

Can I use this questioning approach for requirement specification in any software engineering project?▼

Yes, you can use this questioning approach for requirement specification in any software engineering project. It applies broadly to project planning and feature development, ensuring objectives and constraints are safely clarified through minimal, effective discovery workflows.

What are the limitations of using minimal questions for project clarification?▼

The limitation of using minimal questions for project clarification is that only material ambiguities are addressed. If a project requires exhaustive detail or lacks tools to facilitate question asks and decision recording, this approach may not capture all necessary implementation constraints.