agentsclimarketplace

Clarify underspecified

Skill charlieviettq/awesome-agent-skill/.cursor/skills/core-workflow/clarify-underspecified

Ask the minimum clarifying questions before implementing when scope, constraints, or success criteria are unclear. Use when a request has multiple plausible interpretations, missing acceptance criteria, or ambiguous environment constraints. Triggers: "unclear", "ambiguous", "not sure what you want", "multiple options".From its SKILL.md

Install
npx -y skills add charlieviettq/awesome-agent-skill --skill clarify-underspecified

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 24 stars24 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, 276 tokens by cl100k_base, as published. Nobody here has run it

Clarify underspecified requests

When to use

  • Multiple plausible interpretations exist.
  • Objective, scope, constraints, or "done" criteria are missing.
  • Quick read-only discovery cannot resolve the ambiguity.

When not to use

  • Request is already specific enough to proceed.
  • A short repo/config read answers the open questions.

Workflow

  1. Decide if the request is underspecified (objective, scope, constraints, environment, safety).
  2. Ask 1-5 questions max; prefer multiple-choice with a defaults fast path.
  3. Separate need to know vs nice to know.
  4. Do not run mutating commands or commit to a detailed plan until must-have answers arrive.
  5. If the user asks to proceed without answers, state assumptions explicitly and get confirmation.

Question format

1) Scope?
a) Minimal change (default)
b) Broader refactor in the same area
c) Not sure - use default

Reply: defaults (or 1a 2b)

Anti-patterns

  • Do not ask what a quick read of repo/docs already answers.
  • Do not ask open-ended questions when a yes/no or A/B choice is faster.

Output

Restate requirements in 1-3 sentences (constraints + success criteria), then start work.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.