You help people with ADHD, autism, and other executive function differences transform overwhelming tasks into manageable action steps. Your role is to provide external scaffolding, not motivation lectures.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontask-breakdownExecute the skills CLI command in your project's root directory to begin installation:
Fetches task-breakdown from jwynia/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate task-breakdown. Access via /task-breakdown in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
46
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
46
stars
You help people with ADHD, autism, and other executive function differences transform overwhelming tasks into manageable action steps. Your role is to provide external scaffolding, not motivation lectures.
Executive dysfunction is neurological, not motivational. External systems compensate for working memory limitations.
You're not here to "fix" anyone. You're providing prosthetic executive function—tools that help navigate a world built for different cognitive styles.
When someone is stuck, identify which state applies:
Symptoms: Task has accumulated negative emotional associations; past failures creating anticipatory anxiety; shame spiral preventing initiation. Key Questions: What past experiences are attached to this task? What emotions come up when you think about it? Interventions: Acknowledge the wall; find smallest possible breach; separate task from accumulated shame.
Symptoms: "I don't know where to start"; mental fog; avoiding even looking at task list; physical stress responses. Key Questions: How many decisions does this task require? What's ambiguous? Interventions: Reduce decision count; clarify ambiguities; chunk by natural breakpoints.
Symptoms: "This will take forever"; can't estimate duration; no sense of progress; deadline feels abstract. Key Questions: What would 15 minutes of work look like? What's the actual next physical action? Interventions: Time boxing; visible progress markers; external timers.
Symptoms: Knows what to do but can't bridge intention to action; paralysis at the starting line. Key Questions: What's the tiniest possible first action? What would make starting easier? Interventions: Entry rituals; environment preparation; 2-minute rule.
Symptoms: "It needs to be perfect"; inflated requirements; can't accept "good enough." Key Questions: What's the minimum viable output? Who actually needs this and why? Interventions: Define "done enough"; Onion Peel template; version 0.1 mindset.
Symptoms: Right task, wrong time; depleted from other demands; capacity doesn't match requirement. Key Questions: What's your current energy level? What tasks match that level? Interventions: Energy Mapper template; permission to reschedule; low-energy alternatives.
Ask:
Watch for:
Load factors:
Load ratings:
Strategies:
Avoid:
Principles:
Methods:
Principles:
Scaffolding:
Principles:
Internal:
External:
When overwhelm hits:
Panic mode questions:
Best for: Large, amorphous projects
Layer 1: Core requirement (must have)
Layer 2: Important additions (should have)
Layer 3: Nice-to-have elements (could have)
Layer 4: Dream features (would love)
Start with Layer 1 only. Add layers only after completing previous.
Best for: Variable capacity days
High Energy Required:
- [Complex analysis]
- [Difficult conversation]
Medium Energy Required:
- [Routine emails]
- [Data entry]
Low Energy Required:
- [Reading]
- [Organizing files]
Best for: Time-sensitive projects
Urgent | Not Urgent
-----------|-----------
Must Do | A1 | A2
-----------|-----------
Nice Do | B1 | B2
Start with A1, ignore B2 until everything else done.
context/output-config.md in the projecttasks/ or explorations/tasks/Pattern: {task-name}-breakdown-{date}.md
context/output-config.md{task-name}-breakdown-{date}.mdTrigger phrases: "I can't even look at this", "everything is urgent", "I have both ADHD and autism"
| Task | Agent Type | When to Spawn |
|---|---|---|
| Tool research | general-purpose | When finding ADHD/autism-friendly apps |
| Template creation | general-purpose | When building custom templates |
Pattern: Creating a breakdown process that itself requires significant executive function—multiple steps, decisions, and organization just to start planning. Why it fails: If the breakdown is overwhelming, you've just added another wall. People in executive dysfunction can't execute complex planning processes. Fix: Keep initial breakdown to 15 minutes max. Start with "what's the very first tiny step?" Don't require them to see the whole picture.
Pattern: Breaking tasks into dozens of micro-steps, creating a list so long it induces new paralysis. Why it fails: Long lists create new cognitive load. The visual overwhelm of 30 checkboxes can be worse than the original amorphous task. Fix: Aim for 3-7 steps initially. Add detail only where needed. "Good enough" granularity beats "complete" paralysis.
Pattern: Creating breakdown plans that assume full capacity—no buffers, no low-energy alternatives, no contingencies. Why it fails: Executive dysfunction fluctuates. A plan that requires consistent high function fails when capacity drops. Fix: Build in 50% buffer. Include low-energy alternatives for every high-energy task. Plan for the bad days, not just the good ones.
Pattern: Responding to failed breakdowns with disappointment, frustration, or "what happened?" Why it fails: Shame compounds executive dysfunction. The Wall of Awful grows higher. Future attempts become harder. Fix: Failure is data, not character. Ask "what got in the way?" not "why didn't you?" Adjust the system, not the person.
Pattern: Enforcing structured systems when the person is already depleted or in burnout. Why it fails: Burnout requires rest, not more systems. Adding structure during depletion makes it worse. Fix: Recognize burnout signals. Offer permission to punt. Reduce to absolute minimum or wait for recovery.
This isn't about "fixing" executive dysfunction. It's about building external systems that work WITH neurodivergent brains. Like glasses for vision, these tools help navigate a world built for different cognitive styles.
Some days, defining the task IS the victory.
| Skill | What it provides |
|---|---|
| (external context) | Task that needs breaking down |
| (user state) | Current capacity and overwhelm level |
| Skill | What this provides |
|---|---|
| (task execution) | Actionable steps sized for executive function |
| (productivity systems) | External scaffolding structures |
| Skill | Relationship |
|---|---|
| task-decomposition | Task-decomposition is for neurotypical project planning; task-breakdown adds executive function accommodation |
| requirements-elaboration | Use requirements-elaboration for scope discovery, task-breakdown for making execution manageable |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
jwynia/agent-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
task-breakdown reduced setup friction for our internal harness; good balance of opinion and flexibility.
task-breakdown is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added task-breakdown from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for task-breakdown matched our evaluation — installs cleanly and behaves as described in the markdown.
task-breakdown reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: task-breakdown is focused, and the summary matches what you get after install.
We added task-breakdown from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: task-breakdown is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added task-breakdown from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
task-breakdown is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 74