clarifylisted
Install: claude install-skill TsukiNi22/ai-utils
# Clarify the request before acting
The request is **not** done yet: first make sure it is understood. Everything unclear is asked to the user with
`interactive-questions` (AskUserQuestion popup, never a list in the text), then the work starts on the answers.
**Request given with the skill:** the text after `/clarify` if any, otherwise the latest request of the user.
## 1. Read the request and look
- Read the request as written, then the context that can answer by itself (the code, `git status`, the README,
the conversation, memory): **never ask what can be found or decided from them**; a harmless default is taken and
said in one line.
- Quick read-only look only (files, grep, `git`): no change, no build, no commit during this step.
## 2. List the doubts
Go through the request and keep only the points whose answer **changes what will be done**:
- **Target / scope**: which files, modules, projects, repositories, branches; how far (only this or everything
similar); what must not be touched.
- **Ambiguous words**: "this", "it", "the repo", "etc.", "clean", "update", "like before", two possible meanings.
- **Missing details**: name, version, format, language, output (file / text / PDF), limits, deadline, defaults.
- **Several valid approaches** with different cost, risk or result (the choice is the user's).
- **Contradictions** between parts of the request, or with the code / earlier instructions / conventions.
- **Risky or irreversible actions** (delete, overwrite, for