Agent skill · operations · sickn33
ask-questions-if-underspecified
Clarify requirements before implementing. Use when serious doubts arise.
Why this skill is useful
Codifies a structured approach to clarifying requirements, reducing ambiguity in project specifications.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Ask Questions If Underspecified When to Use Use this skill when a request has multiple plausible interpretations or key details (objective, scope, constraints, environment, or safety) are unclear. When NOT to Use Do not use this skill when the request is already clear, or when a quick, low-risk discovery read can answer the missing details. Goal Ask the minimum set of clarifying questions needed to avoid wrong work; do not start implementing until the must-have questions are answered (or the user explicitly approves proceeding with stated assumptions). Workflow 1) Decide whether the request is underspecified Treat a request as underspecified if after exploring how to perform the work, some or all of the following are not clear: Define the objective (what should change vs stay the same) Define "done" (acceptance criteria, examples, edge cases) Define scope (which files/components/users are in/out) Define constraints (compatibility, performance, style, deps, time) Identify environment (language/runtime versions, OS, build/test runner) Clarify safety/reversibility (data migration, rollout/rollback, risk) Multiple interpretations justify a question only when they materially change the outcome or risk; resolve routine reversible details from the existing context. 2) Ask must-have questions first (keep it small) Ask 1-5 questions in the first pass. Prefer questions that eliminate whole branches of work. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/ask-questions-if-underspecified--4e570c