Task Decomposition

When a task feels too big to estimate or you're paralyzed by where to start, this breaks it down into manageable pieces using vertical slicing, walking skeletons, and dependency analysis. It's grounded in cognitive limits (working memory caps at 7 concepts, tasks over 3 days have 60% completion rates vs 95% for sub-2-hour chunks) and includes diagnostic states like "no clear entry point" or "scope creep" with specific interventions for each. The checklist is solid, the anti-patterns section calls out real problems like unbounded research, and it pushes you toward shipping smallest viable versions. Pairs well with github-agile for actually tracking the decomposed work. Best used before estimation, not during implementation.

skills.sh installs: 599
GitHub stars: 182
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jwynia/agent-skills --skill task-decomposition --agent claude-code

Installs into .claude/skills of the current project.

Files

Task Decomposition Diagnostic

Transform overwhelming development tasks into manageable units by respecting cognitive limits, creating clear boundaries, and enabling parallel work. Tasks properly decomposed achieve 3x higher completion rates and 60% fewer defects.

When to Use This Skill

Use this skill when:

A task feels too big to estimate
Unsure where to start
Blocked by dependencies
Task keeps growing (scope creep)
Need to break down an epic or feature

Do NOT use this skill when:

Task is already small and clear
Doing implementation work
Architecture decisions needed (use system-design)

Core Principle

The goal isn't more tasks—it's the right tasks. Tasks small enough to understand completely, large enough to deliver value, independent enough to avoid blocking.

Quick Reference: Cognitive Limits

Limit	Threshold	Implication
Working memory	7±2 items	Max concepts per task
Context switch recovery	23 minutes	Minimize task switching
Files examined	15-20 max	Bound task scope
Days before completion drops	2-3 days	Keep tasks under this