task-breakdownlisted

# Task Breakdown Break down the feature or epic: **$ARGUMENTS** (granularity defaults to detailed) ## Steps 1. **Understand the scope** — Read user stories, PRDs, or feature descriptions. If code exists, read the relevant areas to understand current state and what needs to change. 2. **Identify work streams**: - **Backend**: API endpoints, database changes, business logic - **Frontend**: components, pages, forms, state management - **Infrastructure**: deploy config, environment variables, CI changes - **Testing**: unit, integration, e2e tests - **Documentation**: README updates, API docs, ADRs 3. **Break into tasks** — Each task should be: - Completable by one person in 1-3 days - Independently mergeable (or clearly part of a sequence) - Testable on its own 4. **Map dependencies** — Which tasks block others? - Database schema must exist before API endpoints - API endpoints must exist before frontend integration - But: frontend components can be built with mocks in parallel 5. **Suggest implementation order** — Optimize for: - Unblocking parallel work early - Getting a vertical slice working end-to-end first - Reducing risk (hard/uncertain tasks first) ## Output Format ```markdown ## Task Breakdown: <feature> ### Summary - **Total tasks**: N - **Estimated effort**: X days (1 developer) - **Parallelizable**: Y (with 2 developers, ~Z days) ### Critical Path `[Schema] → [API] → [Frontend Integration] → [E2E Tests]` ### Tasks