File contents Clarify
Transforms broad ideas into specific, actionable requirements.
Process
1. Clarify the "What"
Ask the user to clarify:
Who is this for? (users, internal team, enterprise)
What's the core value? (one sentence)
What's the MVP scope? (must-have vs nice-to-have)
2. Define Requirements
Output structured requirements:
## Project: [Name]
### Users
- Primary: [user type]
- Secondary: [user type]
### Core Features (MVP)
1. [Feature] - [1 sentence description]
2. [Feature] - [1 sentence description]
### Out of Scope
- [Feature]
- [Feature]
### Tech Stack (Suggested)
- Frontend: [framework]
- Backend: [runtime]
- Database: [type]
- Auth: [approach]
### Success Metrics
- [Metric 1]
- [Metric 2]
3. Break Into Tasks
Convert requirements into issues/tasks:
Each feature = one task
Each task has acceptance criteria
Dependencies noted
Questions to Ask
Category
Questions
Scope
"What's the minimum viable version?"
Users
"Who will use this? What's their technical level?"
Auth
"Do you need user accounts? Social login?"
Data
"What data will you store? Any sensitive info?"
Scale
"How many users? Current/predicted?"
Integrations
"Any external services? (payments, email, etc.)"
Budget
"Any budget constraints?"
Example
Input: "I want to build a habit tracker"
Output:
## Project: Habit Tracker
### Users
- Primary: Individuals tracking personal habits
- Secondary: None (personal app)
### Core Features
1. Daily habit logging - Check off habits each day
2. Streaks - Track consecutive days
3. Statistics - Weekly/monthly progress charts
4. Reminders - Push notifications (future)
### Out of Scope
- Social features
- Team/group tracking
- Premium features
### Tech Stack
- Frontend: Next.js + Tailwind
- Backend: Next.js API routes
- Database: PostgreSQL (Supabase)
- Auth: Email magic link
### Tasks
- [ ] Setup project with Next.js + Supabase
- [ ] Create habits table with user relation
- [ ] Build daily check-in UI
- [ ] Implement streak calculation
- [ ] Add statistics dashboard
1 --- 2 name: clarify 3 description: Clarify 4 --- 5 6 # Clarify 7 8 **Transforms broad ideas into specific, actionable requirements.** 9 10 ## Process 11 12 ### 1. Clarify the "What" 13 14 Ask the user to clarify: 15 - Who is this for? (users, internal team, enterprise) 16 - What's the core value? (one sentence) 17 - What's the MVP scope? (must-have vs nice-to-have) 18 19 ### 2. Define Requirements 20 21 Output structured requirements: 22 23 ```markdown 24 ## Project: [Name] 25 26 ### Users 27 - Primary: [user type] 28 - Secondary: [user type] 29 30 ### Core Features (MVP) 31 1. [Feature] - [1 sentence description] 32 2. [Feature] - [1 sentence description] 33 34 ### Out of Scope 35 - [Feature] 36 - [Feature] 37 38 ### Tech Stack (Suggested) 39 - Frontend: [framework] 40 - Backend: [runtime] 41 - Database: [type] 42 - Auth: [approach] 43 44 ### Success Metrics 45 - [Metric 1] 46 - [Metric 2] 47 ``` 48 49 ### 3. Break Into Tasks 50 51 Convert requirements into issues/tasks: 52 1. Each feature = one task 53 2. Each task has acceptance criteria 54 3. Dependencies noted 55 56 ## Questions to Ask 57 58 | Category | Questions | 59 |----------|-----------| 60 | Scope | "What's the minimum viable version?" | 61 | Users | "Who will use this? What's their technical level?" | 62 | Auth | "Do you need user accounts? Social login?" | 63 | Data | "What data will you store? Any sensitive info?" | 64 | Scale | "How many users? Current/predicted?" | 65 | Integrations | "Any external services? (payments, email, etc.)" | 66 | Budget | "Any budget constraints?" | 67 68 ## Example 69 70 **Input:** "I want to build a habit tracker" 71 72 **Output:** 73 ```markdown 74 ## Project: Habit Tracker 75 76 ### Users 77 - Primary: Individuals tracking personal habits 78 - Secondary: None (personal app) 79 80 ### Core Features 81 1. Daily habit logging - Check off habits each day 82 2. Streaks - Track consecutive days 83 3. Statistics - Weekly/monthly progress charts 84 4. Reminders - Push notifications (future) 85 86 ### Out of Scope 87 - Social features 88 - Team/group tracking 89 - Premium features 90 91 ### Tech Stack 92 - Frontend: Next.js + Tailwind 93 - Backend: Next.js API routes 94 - Database: PostgreSQL (Supabase) 95 - Auth: Email magic link 96 97 ### Tasks 98 - [ ] Setup project with Next.js + Supabase 99 - [ ] Create habits table with user relation 100 - [ ] Build daily check-in UI 101 - [ ] Implement streak calculation 102 - [ ] Add statistics dashboard 103 ```
commit 6051fe8a3f
Frequently asked questions How do I install the Clarify skill? Run npx skillmds@latest add amcamargoc/clarify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
What does the Clarify skill do? Clarify It is listed under Coding & Dev Tools on SkillMD.
Is Clarify safe to use? This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
Which AI agents work with Clarify? This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Is Clarify free to use? Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
Who published Clarify? amcamargoc (@amcamargoc) published this skill. Their other Agent Skills are listed on their SkillMD profile.
amcamargoc