clarify
Ask questions if underspecified. Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Security Assessment
About clarify
The 'clarify' skill is designed to ensure that tasks and requests are fully understood before any implementation begins. It addresses the common problem of ambiguous or incomplete requirements, which can lead to wasted effort, mistakes, or misaligned outcomes. By explicitly identifying areas of uncertainty and prompting the user for essential information, this skill minimizes the risk of incorrect work and facilitates a more structured approach to problem-solving.
The skill provides a systematic workflow for assessing whether a request is underspecified and for gathering the necessary clarifications. It prioritizes must-have questions, keeping the initial set small and focused on eliminating major ambiguities. The skill emphasizes concise, multiple-choice questions with default or recommended options and fast-path responses to reduce friction. Additionally, it supports safe discovery steps and clearly documents assumptions if the user chooses to proceed without full answers. The process concludes with a restatement of requirements to confirm understanding before taking further action.
This skill is particularly useful for developers, project managers, or any professionals who handle complex technical tasks where clarity is critical. It is ideal for situations involving code changes, system configurations, or multi-component projects where assumptions could lead to errors. By enforcing a disciplined approach to clarification, it helps teams maintain alignment, reduce rework, and improve the overall quality and predictability of outcomes.
FAQ
When should I use the 'clarify' skill?
Use it whenever a request is ambiguous or lacks essential details. It should be invoked explicitly and not automatically for every task.
Can I proceed without answering all the clarifying questions?
Yes, but you must explicitly request to proceed. The skill will list assumptions and require confirmation before continuing.
What types of questions does the skill focus on?
It focuses on must-have questions about objectives, scope, constraints, environment, and acceptance criteria, prioritizing multiple-choice or easy-to-answer formats.
Is the skill compatible with different programming languages or project types?
Yes, it is language-agnostic and can be applied to any technical project where clarity and explicit requirements are important.
Are there situations where the skill should not be used?
Do not use it for information that can be obtained with a quick, low-risk discovery read, or for open-ended questions that do not significantly reduce ambiguity.
Install clarify
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
paulopacitti/dotfiles