Transform vague or ambiguous requirements into precise, actionable specifications through structured questioning. Use when user says "clarify", "refine requirements", or when requirements are unclear, incomplete, or open to multiple interpretations. Always use before implementing any ambiguous feature request.
/plugin marketplace add corca-ai/claude-plugins/plugin install clarify@corca-pluginsThis skill is limited to using the following tools:
AskUserQuestion to resolve ambiguities iterativelyRecord the original requirement exactly as stated:
## Original Requirement
"{user's original request verbatim}"
Identify ambiguities using the categories below (see Ambiguity Categories).
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()
After clarification is complete, present the transformation:
## Requirement Clarification Summary
### Before (Original)
"{original request verbatim}"
### After (Clarified)
**Goal**: [precise description of what user wants]
**Reason**: [the ultimate purpose or jobs to be done]
**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] |
Use AskUserQuestion to ask if the user wants to save the clarified requirement:
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? |
| Reason | Why are you doing this? What are jobs to be done? |
| Success | How to verify we're taking the right steps? |
Original: "Add a login feature"
Clarifying questions (via AskUserQuestion):
Clarified:
Original: "The export is broken"
Clarifying questions:
Clarified:
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
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.
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.