task-decomposition

# 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 steps: ``` Task: Checkout flow Step 1: Cart validation — stock check, quantities, totals Step 2: Payment — collect details, validate, process Step 3: Order creation — record, payment link, inventory update Step 4: Confirmati...