Skip to content
Back to skills

Task Decomposition

ASecurity

Breaks features into atomic, independently verifiable tasks. No task should take more than 4 hours. Unblocks parallel work and reduces integration risk.

  • 65 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 26, 2026
developmentgoapisecurity

Works with

  • cursor
  • api

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add DevelopersGlobal/ai-agent-skills --skill task-decomposition --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Task Decomposition?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Task Decomposition
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/developersglobal-task-decomposition/badge)](https://www.skillsdirectory.com/skills/developersglobal-task-decomposition)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: task-decomposition
description: Breaks features into atomic, independently verifiable tasks. No task should take more than 4 hours. Unblocks parallel work and reduces integration risk.
category: plan
applies-to: [claude, gemini, cursor, copilot, any]
version: 1.0.0
---

## Overview

Large tasks fail in large ways. Decomposed tasks fail in small, fixable ways. This skill breaks any feature or project into atomic tasks — each independently implementable, testable, and deployable.

## When to Use

- Before starting any feature that takes more than half a day
- When a task feels overwhelming or unclear
- When multiple people need to work in parallel

## Process

### Step 1: Identify the Deliverable

1. State what "done" looks like for the whole feature.
2. List all the things that must be true when it's complete.
3. Identify dependencies: what must exist before any task can start?

**Verify:** You can state the full feature goal in 2 sentences.

### Step 2: Decompose Into Atomic Tasks

4. Break the feature into tasks where each task:
   - Can be completed in under 4 hours
   - Has a single, clear output
   - Can be verified independently
   - Can be reverted without breaking other tasks
5. Each task should be: `[verb] [noun] so that [outcome]`
   - ✅ "Add rate limiting to /api/login so that brute-force is prevented"
   - ❌ "Work on the login security stuff"

**Verify:** Every task is under 4 hours. Every task has a clear verify condition.

### Step 3: Order and Parallelism

6. Draw the dependency graph — what blocks what?
7. Identify tasks that can be done in parallel.
8. Sequence tasks so integration happens incrementally (not as one big bang at the end).

**Verify:** The dependency order is clear. No unnecessary sequential dependencies.

### Step 4: Estimate and Adjust

9. For each task, estimate: best case / worst case / expected.
10. If any task's worst case > 1 day: decompose further.
11. Total estimate sanity check: does it add up to a reasonable timeline?

## Common Rationalizations (and Rebuttals)

| Excuse | Rebuttal |
|--------|----------|
| "I'll figure it out as I go" | Decomposition takes 30 minutes. Rework from poor planning takes days. |
| "It's too complex to break down" | Everything can be decomposed. Start with what you know, decompose the rest later. |
| "The tasks are too granular" | Granular tasks ship continuously. Coarse tasks ship never. |

## Verification

- [ ] Each task is under 4 hours
- [ ] Each task has a single verify condition
- [ ] Dependencies mapped — no circular dependencies
- [ ] Parallel work identified

## References

- [goal-driven-execution skill](../goal-driven-execution/SKILL.md)
- [multi-agent-orchestration skill](../multi-agent-orchestration/SKILL.md)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…