task-decomposition

1# Task Decomposition
2 
3You are breaking down a complex task into smaller, atomic units. Each unit should be independently completable and verifiable.
4 
5## Core Principle
6 
7**If a task feels too big, it is too big. Break it down until each piece is obvious.**
8 
9A 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.
10 
11## Decomposition Techniques
12 
13### 1. Vertical Slicing
14 
15Break by user-visible functionality (each slice is deployable and testable independently):
16 
17```
18Feature: User Registration
19  Slice 1: Email/password signup — form, validation, account creation
20  Slice 2: Email verification — send email, verify link, UI state
21  Slice 3: Social login (OAuth) — Google button, OAuth flow, account link
22```
23 
24### 2. Horizontal Layering
25 
26Break by system layer:
27 
28```
29Feature: Order Processing
30  Layer 1: Data Model       — entities, migrations
31  Layer 2: Data Access      — repository, CRUD, queries
32  Layer 3: Business Logic   — service, validation rules
33  Layer 4: API Endpoints    — routes, error handling
34  Layer 5: Frontend         — form, API client, loading/error states
35```
36 
37### 3. Workflow Decomposition
38 
39Break by process steps:
40 
41```
42Task: Checkout flow
43  Step 1: Cart validation   — stock check, quantities, totals
44  Step 2: Payment           — collect details, validate, process
45  Step 3: Order creation    — record, payment link, inventory update
46…