---
name: clarify-ambiguous-requests
description: Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
category: general
---

# Clarify Ambiguous Requests

When the task or constraint is unclear, do not guess — ask.

**Process:**
1. Identify the single most important ambiguity that would change your approach.
2. Ask exactly one targeted question. Do not ask several at once.
3. Wait for the user's answer before proceeding.

**Example triggers:** vague scope ("make it better"), missing required input (file path, API key, model name), conflicting constraints, unknown audience.

**Anti-pattern:** Proceeding with assumptions and delivering the wrong result.