ask-questions

Identify missing objectives, scope, and acceptance criteria in task requests.

2|Updated Oct 30, 2025

Search Tags:#workflow #planning #requirements #clarification #ambiguity #prompting

Ready to run

npx skills add https://github.com/zachmayer/skills --skill ask-questions-zachmayer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ask-questions
Source: https://github.com/zachmayer/skills/tree/main/.claude/skills/ask-questions
Command: npx skills add https://github.com/zachmayer/skills --skill ask-questions-zachmayer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents wasted effort and incorrect implementations by forcing a structured clarification process when user requests are vague, underspecified, or lack clear acceptance criteria.

Core Features & Use Cases

Ambiguity Detection: Evaluates requests against objective, scope, constraint, and safety criteria to determine if they are ready for execution.
Structured Inquiry: Generates concise, high-impact questions that eliminate entire branches of incorrect work.
Use Case: When a user provides a broad instruction like "refactor this project," the skill prompts for specific scope boundaries and performance constraints before any code is modified.

Quick Start

Apply the ask-questions skill to evaluate the current task request for missing requirements and formulate clarifying questions.

Frequently Asked Questions about ask-questions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I eliminate ambiguity in underspecified software requirements?▼

To eliminate ambiguity in underspecified software requirements, you evaluate requests against objective, scope, and safety criteria to generate high-impact questions that extract missing acceptance criteria before execution begins.

What is the best way to prevent incorrect implementations from vague task requests?▼

Preventing incorrect implementations from vague task requests requires detecting ambiguity during the initial planning phase and generating concise, high-impact questions that eliminate entire branches of incorrect work.

How do I clarify project scope when given broad refactoring instructions?▼

To clarify project scope when given broad refactoring instructions, prompt for specific scope boundaries and performance constraints before modifying any code, ensuring the request meets defined acceptance criteria.

When do I need to prompt for missing objectives during a development cycle?▼

You need to prompt for missing objectives during the initial planning phase of a development cycle when user requests lack clear acceptance criteria, preventing execution on ambiguous instructions.

Does resolving underspecified task requests require existing project context?▼

Resolving underspecified task requests requires integration with a knowledge-system to leverage existing project context and memory, enabling the formulation of informed clarifying questions during the planning phase.