This skill should be used when the user asks to "clarify requirements", "refine requirements", "specify requirements", "what do I mean", "make this clearer", or when the user's request is ambiguous and needs iterative questioning to become actionable. Also trigger when user says "clarify", "/clarify", or mentions unclear/vague requirements.
Transforms vague requirements into precise specifications through iterative questioning. Triggers when users ask to clarify requirements or make ambiguous requests clearer.
/plugin marketplace add team-attention/plugins-for-claude-natives/plugin install clarify@team-attention-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Transform vague or ambiguous requirements into precise, actionable specifications through iterative questioning.
When requirements are unclear, incomplete, or open to multiple interpretations, use structured questioning to extract the user's true intent before any implementation begins.
Record the original requirement exactly as stated:
## Original Requirement
"{user's original request verbatim}"
Identify ambiguities:
Use AskUserQuestion tool to resolve each ambiguity. Continue until ALL aspects are clear.
Question Design Principles:
Loop Structure:
while ambiguities_remain:
identify_most_critical_ambiguity()
ask_clarifying_question() # Use AskUserQuestion tool
update_requirement_understanding()
check_for_new_ambiguities()
AskUserQuestion Format:
question: "What authentication method should be used?"
options:
- label: "Username/Password"
description: "Traditional email/password login"
- label: "OAuth"
description: "Google, GitHub, etc. social login"
- label: "Magic Link"
description: "Passwordless email link"
After clarification is complete, present the transformation:
## Requirement Clarification Summary
### Before (Original)
"{original request verbatim}"
### After (Clarified)
**Goal**: [precise description of what user wants]
**Scope**: [what's included and excluded]
**Constraints**: [limitations, requirements, preferences]
**Success Criteria**: [how to know when done]
**Decisions Made**:
| Question | Decision |
|----------|----------|
| [ambiguity 1] | [chosen option] |
| [ambiguity 2] | [chosen option] |
Ask if the user wants to save the clarified requirement:
AskUserQuestion:
question: "Save this requirement specification to a file?"
options:
- label: "Yes, save to file"
description: "Save to requirements/ directory"
- label: "No, proceed"
description: "Continue without saving"
If saving:
requirements/ or project-appropriate directoryauth-feature-requirements.md)Common types to probe:
| Category | Example Questions |
|---|---|
| Scope | What's included? What's explicitly out? |
| Behavior | Edge cases? Error scenarios? |
| Interface | Who/what interacts? How? |
| Data | Inputs? Outputs? Format? |
| Constraints | Performance? Compatibility? |
| Priority | Must-have vs nice-to-have? |
Original: "Add a login feature"
Clarifying questions (via AskUserQuestion):
Clarified:
Original: "The export is broken"
Clarifying questions:
Clarified:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.