Task Breakdown

• Rigid systems fail during stress/burnout
• Multiple pathways to completion
• Adaptable to energy fluctuations
• "Good enough" options prevent all-or-nothing paralysis

3. Interest-Based Nervous System Accommodation

• ADHD brains respond to: Interest, Challenge, Novelty, Urgency
• Autistic brains need: Predictability, Clear parameters, Sensory considerations
• Both benefit from: Personal meaning, Special interest integration

Diagnostic States

When someone is stuck, identify which state applies:

State T1: The Wall of Awful

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.

State T2: Cognitive Overload

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.

State T3: Time Blindness

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.

State T4: Task Initiation Block

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.

State T5: Perfectionism Paralysis

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.

State T6: Energy-Task Mismatch

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.

The DECOMPOSE Method

D - Define the Actual Requirement

Ask:

• What is the absolute minimum deliverable?
• What would "done enough" look like?
• Who needs this and why?
• What's negotiable vs. non-negotiable?

Watch for:

• Perfectionism inflation
• Scope creep from anxiety
• Assumed requirements that aren't real

E - Estimate Cognitive Load

Load factors:

• Number of decisions required
• Ambiguity level (high ambiguity = high load)
• Sensory demands
• Social interaction requirements

Load ratings:

• 🟢 Low: Routine, clear, single-focus
• 🟡 Medium: Some decisions, moderate complexity
• 🔴 High: Many decisions, high ambiguity

C - Chunk by Natural Breakpoints

Strategies:

• By Duration: 10/25/45 minute blocks
• By Decision: One decision per chunk
• By Energy: High/medium/low cognitive demand
• By Context: Location, tools, people involved
• By Outcome: Visible progress markers

Avoid:

• Chunks requiring multiple context switches
• Vague chunks ("work on project")
• Chunks without clear completion criteria

O - Order by Energy and Dependencies

Principles:

• Energy matching: High-demand tasks when fresh
• Momentum building: Easy wins first
• Context batching: Similar tasks together
• Interest hacking: Boring tasks between engaging ones

M - Make It Visible

Methods:

• Physical sticky notes (satisfying to remove)
• Digital kanban boards
• Checkbox lists for completion dopamine
• Progress bars for linear progress

Principles:

• One system, not multiple
• Accessible without effort
• Shows both progress and remaining

P - Prepare Transition Bridges

Scaffolding:

• Entry rituals: Same music, drink, location
• Task primers: Review yesterday's progress
• Cognitive bridges: "The next tiny step is..."
• Exit rituals: Note stopping point for tomorrow

O - Optimize for Iteration

Principles:

• First draft is discovery, not delivery
• "Swiss cheese" approach—poke holes anywhere
• Version 0.1 beats version 0.0
• Regular "good enough" checkpoints

S - Support Structures

Internal:

• Body doubling (virtual or in-person)
• Accountability buddies
• Time boxing with external timers
• Reward systems that work for your brain

External:

• Task apps with ADHD features
• AI assistants for breakdown help
• Visual timers for time blindness
• Sensory tools for regulation

E - Emergency Protocols

When overwhelm hits:

1. Stop and breathe (box breathing: 4-4-4-4)
2. Reduce to tiniest possible step
3. Set 5-minute timer for anything
4. Move your body
5. Call in support systems
6. Permission to punt to tomorrow

Panic mode questions:

• What would happen if I did nothing?
• What's the 20% that gets 80% result?
• Who can I ask for help/extension?
• What would bare minimum look like?

Task Templates

Template 1: The Onion Peel

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.

Template 2: The Energy Mapper

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]

Template 3: The Time Box Matrix

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.

Customization by Neurotype

ADHD-Primary

• Emphasize novelty and gamification
• Shorter chunks (10-15 minutes)
• Multiple project rotation
• External accountability critical
• Reward systems for dopamine

Autism-Primary

• Emphasize predictability and routine
• Detailed step specifications
• Sensory environment planning
• Social energy budgeting
• Special interest integration

Combined Presentations

• Flexible structure paradox
• Both novelty AND routine needed
• Extra transition support
• Multiple system options
• Energy/sensory planning crucial

Conversation Approach

For High Overwhelm

• Ultra-gentle approach
• One question at a time
• Offer to do the breakdown for them
• Focus on immediate relief
• Permission to punt/delegate/minimize

For Moderate Overwhelm

• Collaborative breakdown
• 2-3 strategies offered
• Some choice/control given
• Gentle accountability offers

For Low Overwhelm

• More teaching/framework sharing
• Multiple options presented
• Help them self-direct
• Discuss patterns they notice

Language to Use

• "What if we just figured out the very first tiny step?"
• "That sounds really overwhelming. Let's make it smaller."
• "Your brain is working hard—it just needs different supports."
• "What would 'done enough' look like for this?"
• "What's the version that takes 20% effort but gets 80% result?"

Language to Avoid

• "Just break it down into steps" (they would if they could)
• "It's not that hard" (it is for their brain)
• "You should..." (adds pressure)
• "Why didn't you..." (induces shame)
• Any neurotypical productivity advice

Output Persistence

Output Discovery

1. Check for context/output-config.md in the project
2. If found, look for this skill's entry
3. If not found, ask user: "Where should I save task breakdown work?"
4. Suggest: tasks/ or explorations/tasks/

Primary Output

• Diagnostic state - Which overwhelm state applies
• Task decomposition - Using DECOMPOSE method
• Energy mapping - Tasks matched to capacity
• Support structures - External scaffolding identified

File Naming

Pattern: {task-name}-breakdown-{date}.md

Verification (Oracle)

What This Skill Can Verify

• State identification - Which diagnostic state applies? (High confidence)
• Chunk appropriateness - 3-7 chunks, clear completion criteria? (High confidence)
• Energy matching - Tasks matched to current capacity? (Medium confidence)

What Requires Human Judgment

• Actual capacity - What the person can handle right now
• Which interventions fit - What scaffolding works for this person
• When to stop - When breakdown is "good enough"

Oracle Limitations

• Cannot assess actual executive function capacity
• Cannot predict which scaffolding will work

Feedback Loop

Session Persistence

• Output location: See context/output-config.md
• What to save: State, decomposition, energy map, supports
• Naming pattern: {task-name}-breakdown-{date}.md

Cross-Session Learning

• Check for prior breakdown work for this person
• Build on what scaffolding worked before
• Failed approaches inform future interventions

Design Constraints

This Skill Assumes

• User has executive function challenges
• Task feels overwhelming (not just complex)
• External scaffolding would help

This Skill Does Not Handle

• General project planning - Route to: task-decomposition (software)
• Requirements elaboration - Route to: requirements-elaboration
• Motivation/therapy - Route to: appropriate professional support

Degradation Signals

• Breakdown itself becomes overwhelming
• Too many tiny steps (cognitive overload)
• Rigid systems during burnout

Reasoning Requirements

Standard Reasoning

• Single state identification
• Basic DECOMPOSE application
• Simple energy mapping

Extended Reasoning (ultrathink)

• Complex task with Wall of Awful - [Why: emotional history requires careful handling]
• Multi-task prioritization - [Why: competing demands need integrated approach]
• Custom neurotype accommodation - [Why: ADHD/autism combined needs special handling]

Trigger phrases: "I can't even look at this", "everything is urgent", "I have both ADHD and autism"

Execution Strategy

Sequential (Default)

• State diagnosis before intervention
• Define actual requirement before chunking
• Chunk before energy mapping

Parallelizable

• Breaking down multiple independent tasks
• Researching different scaffolding tools

Subagent Candidates

Context Management

Approximate Token Footprint

• Skill base: ~3.5k tokens (foundations + states + DECOMPOSE)
• With templates: ~4.5k tokens
• With customization: ~5k tokens

Context Optimization

• Focus on relevant diagnostic state
• DECOMPOSE method is core
• Templates are reference, load relevant one

When Context Gets Tight

• Prioritize: Current state, emergency protocols
• Defer: Full template library, all customization options
• Drop: Language examples, conversation approach details

Anti-Patterns

1. Overwhelming the Breakdown

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.

2. Step Proliferation

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.

3. Ignoring Capacity Reality

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.

4. Shame Addition

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.

5. Rigidity During Burnout

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.

Remember

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.

Integration

Inbound (feeds into this skill)

Outbound (this skill enables)

Complementary