ask-questions-if-underspecified

Ask targeted questions to define objectives, acceptance criteria, scope, and constraints.

1|Updated Mar 3, 2025

Search Tags:#workflow #scoping #requirements #clarification #underspecified #ask questions

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted effort and incorrect implementations by ensuring all necessary requirements are clearly understood before starting work.

Core Features & Use Cases

Requirement Clarification: Identifies and asks targeted questions about underspecified requests.
Scope Definition: Helps define objectives, acceptance criteria, scope, and constraints.
Use Case: When a user asks to "update the user profile page," this Skill will ask clarifying questions like "Which specific fields need updating?" and "What are the acceptance criteria for a successful update?" before proceeding.

Quick Start

Use the ask questions if underspecified skill to clarify the requirements for updating the user profile page.

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

To clarify underspecified software requirements, ask targeted questions to define project objectives, acceptance criteria, scope, and constraints. This requirement clarification process prevents wasted development effort by ensuring all necessary details are understood before writing code.

What is requirement scoping and when do I need it for development tasks?▼

Requirement scoping is the process of defining boundaries, acceptance criteria, and constraints for a development task. You need it when user requests are underspecified, ensuring clarity on environment, safety, and reversibility before implementation begins.

How do I gather acceptance criteria for an underspecified user request?▼

Gather acceptance criteria by asking targeted questions about the user request's expected outcomes, constraints, and scope. Defining these criteria before implementation ensures the final software deliverable meets the defined success conditions.

What questions should I ask to define the scope and constraints of a feature request?▼

Ask questions targeting objectives, specific functional requirements, environmental factors, and operational limits. Defining scope and constraints before implementation ensures the development effort aligns with safety requirements and reversibility expectations.

Can I use requirement clarification for any software engineering workflow?▼

Yes, requirement clarification applies to any software engineering workflow where requests are underspecified. It helps define objectives and constraints across diverse development environments without requiring specific dependencies or platform prerequisites.

Why does starting implementation without requirement clarification lead to incorrect outputs?▼

Starting implementation without requirement clarification leads to incorrect outputs because objectives, scope, and constraints remain ambiguous. Clarifying these underspecified elements beforehand prevents wasted effort and ensures the code matches actual user expectations.