task-decomposition
Breaks down complex software, writing, or research tasks into small, atomic, independently completable units with dependency graphs and milestone breakdowns. Use when the user asks to plan a project, decompose a feature, create subtasks, split up work, or needs help organizing a large piece of work into a step-by-step plan. Triggered by phrases like "break down", "decompose", "where do I start", "too big", "split into tasks", "work breakdown", or "task list".
Profile →npx skills add rohitg00/skillkit --skill task-decomposition --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Task Decomposition You are breaking down a complex task into smaller, atomic units. Each unit should be independently completable and verifiable. ## Core Principle **If a task feels too big, it is too big. Break it down until each piece is obvious.** A well-decomposed task should take no more than a few hours to complete and have a clear definition of done. Aim for tasks that are small, independent, testable, and clearly scoped. ## Decomposition Techniques ### 1. Vertical Slicing Break by user-visible functionality (each slice is deployable and testable independently): ``` Feature: User Registration Slice 1: Email/password signup — form, validation, account creation Slice 2: Email verification — send email, verify link, UI state Slice 3: Social login (OAuth) — Google button, OAuth flow, account link ``` ### 2. Horizontal Layering Break by system layer: ``` Feature: Order Processing Layer 1: Data Model — entities, migrations Layer 2: Data Access — repository, CRUD, queries Layer 3: Business Logic — service, validation rules Layer 4: API Endpoints — routes, error handling Layer 5: Frontend — form, API client, loading/error states ``` ### 3. Workflow Decomposition Break by process s
- Core Principle
- Decomposition Techniques
- 1. Vertical Slicing
- 2. Horizontal Layering
- 3. Workflow Decomposition
- 4. Component Decomposition
- Task Template
- Dependency Management
- Identify Dependencies
- Minimize Dependencies
- Order by Dependencies
- Decomposition Checklist
- Integration with Other Skills
What does the task-decomposition skill do?
Breaks down complex software, writing, or research tasks into small, atomic, independently completable units with dependency graphs and milestone breakdowns. Use when the user asks to plan a project, decompose a feature, create subtasks, split up work, or needs help organizing a large piece of work into a step-by-step plan. Triggered by phrases like "break down", "decompose", "where do I start", "too big", "split into tasks", "work breakdown", or "task list".
How do I install it?
Run `npx skills add rohitg00/skillkit --skill task-decomposition --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rohitg00/skillkit, a repository with 1,422 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.