clarify-intentlisted

# Clarify Intent A skill for detecting ambiguous user instructions and asking for clarification before starting the task, so the work matches what the user actually needs instead of Claude's own assumptions. ## When an instruction counts as ambiguous An instruction is considered ambiguous if any of the following apply: - It's too generic and could have multiple valid interpretations (e.g. "analyze this file", "fix this document", "make a report", "process this data") - It's unclear what output is expected (a document? a summary? a table? bullet points?) - It's unclear what focus or angle is being asked for (e.g. the file covers many topics and it's unclear which one is meant) - A file is attached but the instruction doesn't say which part to use or for what purpose An instruction is considered **clear** and does NOT trigger this skill when it already specifies a target, format, and scope, for example: - "Extract all invoice numbers from this PDF into a table" - "Translate the 3rd paragraph on page 5 into English" - "Make a bar chart from the sales column in this file" ## How it works 1. If the user's instruction is ambiguous (with or without an attached file), do NOT start the task or make assumptions. 2. If a file is attached, it's fine to skim it (title, table of contents, general structure) to help write relevant questions — but don't start working on the actual task content yet. 3. Compose 5-7 short clarifying questions covering: - The main purpose/intent of th