
Task Breakdown Specialist
- 132 installs
- 33 repo stars
- Updated December 25, 2025
- daffy0208/ai-dev-standards
Convert vague product or engineering goals into scoped milestones, dependency-aware subtasks, and acceptance-sized units suitable for agent execution or human review before build begins.
About
The task-breakdown-specialist skill in ai-dev-standards helps Claude Code turn fuzzy goals into validated scope: clear milestones, explicit dependencies, right-sized tasks, and agent-executable work packets before expensive build and ship cycles begin.
- Ambiguity reduction
- Milestone sequencing
- Dependency mapping
- Acceptance-sized units
- Agent-ready work packets
Task Breakdown Specialist by the numbers
- 132 all-time installs (skills.sh)
- Ranked #1,242 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 30, 2026 (Skillselion catalog sync)
npx skills add https://github.com/daffy0208/ai-dev-standards --skill task-breakdown-specialistAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 132 |
|---|---|
| repo stars | ★ 33 |
| Last updated | December 25, 2025 |
| Repository | daffy0208/ai-dev-standards ↗ |
What it does
Convert vague product or engineering goals into scoped milestones, dependency-aware subtasks, and acceptance-sized units suitable for agent execution or human review before build begins.
Files
Task Breakdown Specialist
Lower activation energy. Build momentum. Make progress visible.
Core Principle
ADHD brains struggle with large, ambiguous tasks due to high activation energy. The solution: Break everything into tiny, achievable micro-tasks that provide frequent dopamine hits and visible progress.
Key Insight: Starting is the hardest part. Make starting ridiculously easy.
---
The ADHD Task Problem
Problem 1: Activation Energy
Issue: "Build authentication system" feels overwhelming Result: Procrastination, anxiety, avoidance
Problem 2: Time Blindness
Issue: Can't estimate how long tasks take Result: Unrealistic plans, missed deadlines, frustration
Problem 3: Working Memory
Issue: Can't hold large task in mind while working Result: Losing track of what you're doing, constant re-reading
Problem 4: Dopamine Deficit
Issue: Big tasks provide no intermediate rewards Result: Motivation loss, task abandonment
---
Phase 1: Quick Win Strategy
Start with 2-Minute Tasks
Why: Zero activation energy, instant dopamine, builds momentum
❌ Bad Task: "Build user authentication"
- Feels huge (overwhelm)
- Unclear start point (paralysis)
- No quick wins (no dopamine)
✅ Good Breakdown:
Quick Wins (Build Momentum) ⚡
1. [ ] Create /auth folder (30 sec) 🟢
2. [ ] Create auth.ts file (30 sec) 🟢
3. [ ] Install bcrypt package (1 min) 🟢
WHY START HERE:
- Combined: 2 minutes total
- Zero thinking required
- 3 quick dopamine hits
- Momentum established
THEN move to real work...The 2-5-15-30 Pattern
Break tasks into time categories:
2-minute tasks (🟢) - Setup, scaffolding, installs 5-minute tasks (🟢) - Simple functions, basic HTML 15-minute tasks (🟡) - Core logic, API calls 30-minute tasks (🟡) - Complex features, integration
Rule: Always start with 2-minute tasks!
---
Phase 2: The Breakdown Formula
Step 1: Capture the Big Task
Write down the overwhelming task:
Big Task: Build user dashboard with analyticsStep 2: Ask Clarifying Questions
Questions:
- What's the absolute minimum? (MVP)
- What would "done" look like?
- What can I skip for now?
- What's P0 vs P1 vs P2?Step 3: Identify Micro-Tasks
Use this template:
## Big Task: Build User Dashboard
### P0 (Must Have - MVP)
- Dashboard page exists
- Shows user name
- Shows one metric (login count)
### P1 (Should Have - Next)
- Charts and graphs
- Multiple metrics
- Time range selector
### P2 (Nice to Have - Later)
- Export data
- Custom widgets
- Real-time updatesStep 4: Break P0 into Micro-Tasks
## Building P0 Dashboard
Phase 1: Quick Wins (Momentum) ⚡
1. [ ] Create dashboard.tsx file (30 sec) 🟢
2. [ ] Add to navigation menu (1 min) 🟢
3. [ ] Add "Dashboard" heading (30 sec) 🟢
Total: 2 minutes
Phase 2: Core Structure 🏗️ 4. [ ] Create dashboard layout (5 min) 🟢 5. [ ] Add user name display (5 min) 🟢 6. [ ] Style with Tailwind (10 min) 🟡
Total: 20 minutes
Phase 3: Data Integration 📊 7. [ ] Fetch user data from API (15 min) 🟡 8. [ ] Display login count (10 min) 🟡 9. [ ] Add loading state (5 min) 🟢
Total: 30 minutes
Phase 4: Polish & Ship ✨ 10. [ ] Handle error states (10 min) 🟡 11. [ ] Test all paths (10 min) 🟡 12. [ ] Deploy (5 min) 🟢
Total: 25 minutes
Grand Total: ~75 minutes
With ADHD tax (1.5x): ~110 minutes (2 hours)---
Phase 3: Task Sizing with ADHD Tax
Standard Time Estimates Are Lies
Neurotypical estimate × 1.5-2 = ADHD estimate
Why:
- Task switching overhead
- Distraction recovery time
- Setup/teardown time
- "Where was I?" moments
- Inevitable rabbit holes
ADHD Time Multipliers
Simple task (5 min estimated):
→ ADHD reality: 7-10 min (1.5x)
Medium task (30 min estimated):
→ ADHD reality: 45-60 min (1.5-2x)
Complex task (2 hours estimated):
→ ADHD reality: 3-4 hours (2x)
New/Unknown task (?? estimated):
→ ADHD reality: 3x whatever you thinkHonest Task Sizing
## Feature: Add password reset
Traditional estimate: 1 hour
ADHD-honest estimate:
- Setup email service (5 min → 10 min)
- Generate reset token (10 min → 15 min)
- Build reset form (20 min → 30 min)
- Handle token validation (15 min → 25 min)
- Test flows (10 min → 20 min)
Subtotal: 60 min → 100 min
- Buffer for interruptions: +20 min
- Debugging time: +30 min
Real estimate: 2.5 hours
👍 Better to overestimate and finish early (dopamine!)
👎 Than underestimate and feel like failure---
Phase 4: Momentum-Based Ordering
Dopamine-Optimized Task Sequence
Don't do tasks in logical order. Do them in motivation order.
❌ Logical Order (ADHD-hostile):
1. Plan architecture (hard, no dopamine)
2. Set up database (boring, no dopamine)
3. Build API (complex, delayed dopamine)
4. Build UI (fun but blocked by above)
✅ Momentum Order (ADHD-friendly):
1. Build UI mockup (fun, instant visual) 🎨 Dopamine!
2. Add fake data (easy, looks real) 🎯 Dopamine!
3. Hook up API (has context now) 💪 Dopamine!
4. Set up database (motivated now) ✅ Dopamine!
5. Refine architecture (understand it now) 🚀 Done!
Why this works:
- Starts with fun (low activation energy)
- Provides instant feedback (dopamine)
- Builds understanding (easier to do hard parts)
- Maintains momentum (no dead zones)The Quick Win Sandwich
Pattern: Easy → Hard → Easy
Session Plan (2 hours):
00:00 - 00:10: Quick wins (3 easy tasks)
→ Builds momentum
→ Establishes "I'm productive" mindset
00:10 - 01:30: Hard task (focus required)
→ You have momentum now
→ Feel accomplished from quick wins
01:30 - 02:00: Easy task (cool down)
→ End on high note
→ Easy to resume tomorrow---
Phase 5: Progress Visualization
Make Progress Visible
ADHD brains need to SEE progress for dopamine release.
Progress Bars
## Feature: User Authentication
Progress: ████████░░ 80%
✅ Phase 1: Setup (20%)
✅ Phase 2: Login (30%)
✅ Phase 3: Signup (30%)
🔄 Phase 4: Reset (20%) ← YOU ARE HERE
Next: Password reset form (15 min)Checklist with Time Tracking
## Today's Tasks
🔥 Streak: 3 days
⏱️ Focus time: 45 min
Morning Session (2 hours budgeted):
- [x] Fix login bug (15 min) ✅ 12 min (faster!)
- [x] Add loading spinner (5 min) ✅ 7 min
- [x] Update tests (10 min) ✅ 15 min
- [ ] Code review (20 min) ← CURRENT
- [ ] Deploy fix (10 min)
Progress: 3/5 tasks (60%)
Time spent: 34 min / 120 min
Remaining: 30 min of work
💪 You're crushing it!Commit-Based Progress
## This Week's Progress
Mon: ✅✅✅✅✅ (5 commits)
Tue: ✅✅✅ (3 commits)
Wed: ✅✅✅✅✅✅✅ (7 commits) 🔥 Best day!
Thu: ✅✅✅✅ (4 commits)
Fri: ✅ (1 commit) ← TODAY
Total: 20 commits this week
Goal: 15 commits (exceeded! 🎉)
Keep the streak alive!---
Phase 6: Task Breakdown Patterns
Pattern 1: Feature Breakdown
# Feature: Add dark mode
## Step 1: Identify Components
What needs to change?
- Colors
- Component styles
- Toggle button
- Persistence
## Step 2: Break Down Each
### Colors (30 min total)
- [ ] Define dark color palette (5 min) 🟢
- [ ] Add CSS variables (10 min) 🟡
- [ ] Test contrast ratios (15 min) 🟡
### Component Styles (45 min total)
- [ ] Update Button component (10 min) 🟡
- [ ] Update Card component (10 min) 🟡
- [ ] Update Input component (10 min) 🟡
- [ ] Update Header component (15 min) 🟡
### Toggle Button (20 min total)
- [ ] Create ThemeToggle component (15 min) 🟡
- [ ] Add to header (5 min) 🟢
### Persistence (15 min total)
- [ ] Save preference to localStorage (10 min) 🟡
- [ ] Load on app start (5 min) 🟢
Total: 110 min (2 hours realistic)Pattern 2: Bug Fix Breakdown
# Bug: Users can't reset password
## Step 1: Reproduce (10 min)
- [ ] Try reset flow locally (5 min) 🟢
- [ ] Check error logs (5 min) 🟢
## Step 2: Investigate (20 min)
- [ ] Find reset-password.ts file (1 min) 🟢
- [ ] Read through code (5 min) 🟢
- [ ] Identify issue (token expiry) (10 min) 🟡
- [ ] Confirm root cause (4 min) 🟢
## Step 3: Fix (30 min)
- [ ] Update token expiry logic (20 min) 🟡
- [ ] Add better error message (10 min) 🟡
## Step 4: Test (15 min)
- [ ] Test locally (10 min) 🟡
- [ ] Test on staging (5 min) 🟢
## Step 5: Deploy (10 min)
- [ ] Create PR (3 min) 🟢
- [ ] Deploy to production (7 min) 🟢
Total: 85 min (1.5 hours)Pattern 3: Learning Task Breakdown
# Learn: Next.js App Router
❌ Bad: "Learn Next.js App Router" (too vague)
✅ Good Breakdown:
## Phase 1: Overview (30 min)
- [ ] Watch official intro video (15 min) 🟢
- [ ] Read "Getting Started" docs (15 min) 🟢
## Phase 2: Hands-On (1 hour)
- [ ] Create new Next.js project (5 min) 🟢
- [ ] Build simple page (15 min) 🟡
- [ ] Add dynamic route (20 min) 🟡
- [ ] Try server components (20 min) 🟡
## Phase 3: Apply (2 hours)
- [ ] Migrate one page in my project (30 min) 🟡
- [ ] Test and debug (30 min) 🟡
- [ ] Migrate second page (30 min) 🟡
- [ ] Document learnings (30 min) 🟡
Total: 3.5 hours over 2 days
Day 1: Phase 1 + 2 (1.5 hours)
Day 2: Phase 3 (2 hours)---
Phase 7: Anti-Patterns (What NOT to Do)
❌ Anti-Pattern 1: Perfectionist Breakdown
Bad:
- [ ] Research best authentication library (no time limit)
- [ ] Compare 10 different approaches (rabbit hole)
- [ ] Design perfect architecture (never starts)
Good:
- [ ] Choose auth library (10 min, use NextAuth)
- [ ] Follow quickstart guide (30 min)
- [ ] Ship MVP, iterate later❌ Anti-Pattern 2: Too Granular
Bad:
- [ ] Open VS Code (10 sec)
- [ ] Navigate to file (10 sec)
- [ ] Type 'import' (5 sec)
This is ridiculous. You'll spend more time reading the list.
Good:
- [ ] Add imports to auth.ts (2 min)❌ Anti-Pattern 3: All Hard Tasks
Bad:
- [ ] Refactor authentication (2 hours)
- [ ] Optimize database queries (3 hours)
- [ ] Fix critical bug (2 hours)
No quick wins = No momentum = No dopamine = Procrastination
Good:
- [ ] Update README (5 min) 🟢 ← Start here!
- [ ] Refactor one function (30 min) 🟡
- [ ] Take break (5 min)
- [ ] Fix critical bug (2 hours) 🟡❌ Anti-Pattern 4: Vague Tasks
Bad:
- [ ] Work on dashboard
- [ ] Fix bugs
- [ ] Improve performance
What does "done" mean? ADHD brain will wander.
Good:
- [ ] Add user stats to dashboard (15 min)
- [ ] Fix login timeout bug (#123) (20 min)
- [ ] Reduce API response time to < 200ms (1 hour)---
Phase 8: Emergency Task Breakdown
When You're Stuck RIGHT NOW
5-Minute Breakdown Exercise:
1. Write the overwhelming task:
_________________________________2. What's the FIRST tiny action? (< 2 min)
_________________________________3. Do ONLY that action. Nothing else.
4. Dopamine hit! Now write next action:
_________________________________5. Repeat.
Example:
1. Overwhelming: "Build entire checkout flow"
2. First tiny action: "Create checkout.tsx file"
3. [DO IT NOW - 30 seconds]
4. ✅ Done! Dopamine!
5. Next action: "Add basic form HTML"
6. [DO IT - 5 min]
7. Keep going...---
Checklist: Good Task Breakdown
Use this to validate your task breakdown:
- [ ] Tasks are 15 minutes or less
- [ ] Starts with 2-3 "quick win" tasks (2-5 min)
- [ ] Each task has clear "done" criteria
- [ ] Time estimates include ADHD tax (1.5x)
- [ ] Uses progress visualization (%, bars, checklists)
- [ ] Easy tasks mixed with hard tasks (momentum maintenance)
- [ ] No vague tasks ("work on", "improve", "fix")
- [ ] Total time estimated honestly (not wishful thinking)
- [ ] First task has near-zero activation energy
---
Tools & Templates
Daily Task Template
# Today: [Date]
## ONE Main Goal
[The ONE thing that matters today]
## Morning Session (2 hours)
Quick Wins:
- [ ] Task 1 (2 min) 🟢
- [ ] Task 2 (5 min) 🟢
Main Work:
- [ ] Task 3 (30 min) 🟡
- [ ] Task 4 (45 min) 🟡
Cool Down:
- [ ] Task 5 (10 min) 🟢
## Afternoon Session (2 hours)
[Same pattern]
## Wins Log
[What you completed - for dopamine]Project Breakdown Template
# Project: [Name]
## MVP Definition
What's the absolute minimum to ship?
## Phases
### Phase 1: Foundation (Quick wins)
- [ ] Tasks...
### Phase 2: Core Features
- [ ] Tasks...
### Phase 3: Polish
- [ ] Tasks...
## Time Estimate
Naive: X hours
ADHD-realistic: Y hours (1.5-2x)---
Related Skills
- context-preserver - Save state between tasks
- focus-session-manager - Manage work sessions
- completion-coach - Finish what you start
- adhd-workflow-architect - Design ADHD-friendly workflows
---
Success Metrics
You're using this skill well when:
- ✅ Starting tasks feels easy (low activation energy)
- ✅ You see progress every 15 minutes
- ✅ Time estimates are realistic
- ✅ You finish tasks instead of abandoning them
- ✅ You feel in control (not overwhelmed)
---
Break it down. Start small. Build momentum. Ship things. 💪
name: task-breakdown-specialist
kind: skill
description: Break large tasks into ADHD-friendly micro-tasks that minimize activation
energy and maximize momentum. Use when feeling overwhelmed, can't start a task,
or need to make progress visible. Optimized for ADHD developers with 15-minute task
chunking and dopamine-driven ordering.
preconditions:
- check: project_initialized
description: Project environment is set up
required: true
effects:
- provides_capability
domains: &id001
- ai
- rag
- api
- frontend
- backend
- security
- testing
- product
- design
- data
- orchestration
cost: medium
latency: medium
risk_level: low
side_effects:
- modifies_files
- creates_artifacts
idempotent: false
success_signal: task-breakdown-specialist capability successfully applied
failure_signals:
- Prerequisites not met
- Configuration error
compatibility:
requires: []
conflicts_with: []
composes_with: []
enables: []
observability:
logs:
- Applying task-breakdown-specialist...
- task-breakdown-specialist completed
metrics:
- execution_time_ms
- success_rate
metadata:
version: 1.0.0
created_at: '2025-10-30'
tags: *id001
examples: []
Task Breakdown Specialist - Quick Start
Version: 1.0.0 Category: ADHD Support Difficulty: Beginner
What This Skill Does
Automatically breaks large, overwhelming tasks into tiny, achievable micro-tasks optimized for ADHD. Reduces activation energy, provides quick wins, and makes progress visible.
When to Use
Use this skill when:
- Feeling overwhelmed by task size
- Can't start a task (activation energy too high)
- Need to make progress visible
- Want to build momentum with quick wins
- Estimating time for tasks
Automatic Activation: Claude uses this skill automatically when you describe a large task or say you're feeling stuck.
Quick Start
Just describe what you need to do:
You: "I need to build user authentication"
Claude: [Automatically uses task-breakdown-specialist]
Quick Wins (Start Here - 2 min): ⚡
1. [ ] Create /auth folder (30 sec)
2. [ ] Create auth.ts file (30 sec)
3. [ ] Install bcrypt (1 min)
Core Work (After momentum):
4. [ ] Build login endpoint (25 min)
5. [ ] Add password hashing (15 min)
...
Total: ~2 hours (ADHD-realistic estimate)
💡 Start with task #1 NOW (30 seconds = easy!)Key Concepts
Activation Energy - The effort needed to start a task
- Large tasks = high activation energy = procrastination
- Tiny tasks = low activation energy = easy to start
Quick Wins - Tasks that take 2-5 minutes
- Build momentum
- Provide immediate dopamine
- Establish "I'm productive" mindset
- Always start with 3 quick wins
ADHD Tax - Reality-based time estimates
- Multiply neurotypical estimates by 1.5-2x
- Accounts for distractions, context switching, "where was I?"
- Better to overestimate and finish early (dopamine!)
Progress Visualization - Make work visible
- Checklists ✅
- Progress bars ████████░░ 80%
- Time tracking
- Dopamine hits from completion
The 2-5-15-30 Pattern
Break tasks into time buckets:
- 2-min tasks 🟢 - Setup, scaffolding (START HERE)
- 5-min tasks 🟢 - Simple functions, basic HTML
- 15-min tasks 🟡 - Core logic, API calls
- 30-min tasks 🟡 - Complex features
Rule: Always start with 2-minute tasks!
Quick Reference
Good Task Breakdown
✅ DO:
- Start with quick wins (2-5 min tasks)
- Keep tasks ≤ 15 minutes
- Use clear "done" criteria
- Include ADHD tax in estimates (1.5-2x)
- Make progress visible
- Mix easy and hard tasks
❌ DON'T:
- Start with hard tasks (high activation energy)
- Make tasks vague ("work on dashboard")
- Use wishful time estimates
- Create all-hard-task lists
- Skip quick wins
Example Breakdown
❌ Bad: "Build dashboard" (overwhelming)
✅ Good:
Quick Wins (2 min total):
- [ ] Create dashboard.tsx (30 sec) 🟢
- [ ] Add to nav menu (1 min) 🟢
- [ ] Add heading (30 sec) 🟢
Core Work (45 min total):
- [ ] Build layout (15 min) 🟡
- [ ] Fetch user data (15 min) 🟡
- [ ] Display stats (15 min) 🟡
Polish (15 min total):
- [ ] Add loading state (5 min) 🟢
- [ ] Handle errors (10 min) 🟡
Total: ~60 min (realistic: 90 min with ADHD tax)Automation Features
Claude automatically:
- ✅ Breaks down large tasks when you describe them
- ✅ Adds 3 quick wins to start
- ✅ Includes ADHD-realistic time estimates
- ✅ Creates progress visualization
- ✅ Reorders tasks for momentum
You just:
- Describe what you need to do
- Start with the first tiny task
- Get dopamine from checking off tasks
Time Estimates (ADHD-Realistic)
Your thought: "This will take 1 hour"
Reality: 1.5-2 hours
Quick task (5 min): → 7-10 min
Medium task (30 min): → 45-60 min
Large task (2 hours): → 3-4 hours
New/unknown: 3x what you think
Better to overestimate! Finishing early = dopamineEmergency Breakdown
Stuck right now?
1. Write the overwhelming task 2. Ask: "What's the FIRST 2-minute action?" 3. Do ONLY that action 4. ✅ Dopamine! 5. Ask: "What's next?" 6. Repeat
Example:
1. Overwhelming: "Build checkout flow"
2. First action: "Create checkout.tsx file" (30 sec)
3. [DO IT]
4. ✅ Done!
5. Next: "Add basic form HTML" (5 min)
6. [DO IT]
7. Keep going...Common Patterns
Feature Breakdown
1. Identify components that change 2. Break each into micro-tasks 3. Start with quick wins 4. Build core features 5. Polish and ship
Bug Fix Breakdown
1. Reproduce (5-10 min) 2. Investigate (10-20 min) 3. Fix (20-30 min) 4. Test (10-15 min) 5. Deploy (5-10 min)
Learning Breakdown
1. Overview (watch video, read intro) 2. Hands-on (build simple example) 3. Apply (use in real project)
Tools & Templates
Daily Task Template:
# Today
ONE Main Goal: [most important thing]
Morning Quick Wins:
- [ ] Task 1 (2 min) 🟢
- [ ] Task 2 (5 min) 🟢
Main Work:
- [ ] Task 3 (30 min) 🟡
Wins Log: [completed tasks for dopamine]Success Metrics
You're using this skill well when:
- ✅ Starting tasks feels easy
- ✅ You complete multiple tasks per session
- ✅ Time estimates are realistic
- ✅ You see progress clearly
- ✅ You feel in control (not overwhelmed)
Related Skills
- context-preserver - Auto-save state between tasks
- focus-session-manager - Automated break reminders
- completion-coach - Auto-detect "90% done" syndrome
- adhd-workflow-architect - Build automated workflows
Version History
- 1.0.0 (2025-10-22): Initial release with full ADHD optimization
License
Part of ai-dev-standards repository.