Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rohitg00/task-decomposition
Breaks down complex software, writing, or research tasks into small, atomic, independently completable units with dependency graphs and milestone breakdowns.
Passed 20 of 22 test cases with the skill, and 5 of 22 without it.
and 31 more in the full report
15 fixed5 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to construct an order processing module for our e-commerce platform. Decompose this work horizontally across architecture layers from data model up to frontend presentation.
| Checked | Without skill | With skill |
|---|---|---|
| Structures work items across architectural layers starting with data model and progressing through data access, logic, API, and UI. | Passed | Passed |
| Formats every decomposed item using the **Files to Create/Modify:** checkbox list. | Missed | Passed |
| Lists explicit dependencies between architectural layers using Requires: and Blocks:. | Missed | Passed |
The instructions your model reads when the skill loads.
You are breaking down a complex task into smaller, atomic units. Each unit should be independently completable and verifiable.
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.
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
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
Break by process steps:
test cases passed, vs 5 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.