task-breakdown

# Task Breakdown

Transform designs into actionable implementation plans. This skill teaches how to create well-structured task lists that enable efficient, systematic development.

## When to Use This Skill

Use task breakdown when:
- Design phase is complete and approved
- Ready to begin implementation
- Need to coordinate work across developers
- Want to track incremental progress
- Planning sprints or work assignments

## Task Structure

### Two-Level Hierarchy

```markdown
- [ ] 1. [Epic/Major Component]
- [ ] 1.1 [Specific implementation task]
  - [Implementation details]
  - [Files/components to create]
  - _Requirements: [Requirement references]_
- [ ] 1.2 [Next specific task]
  - [Details]
  - _Requirements: [References]_

- [ ] 2. [Next Epic/Major Component]
- [ ] 2.1 [Specific task]
```

### Task Specification Elements

Each task should include:
1. **Clear Objective:** What specific code to write/modify
2. **Implementation Details:** Files, components, functions
3. **Requirements Reference:** Which requirements this implements
4. **Completion Criteria:** How to know the task is done

## Step-by-Step Process

### Step 1: Analyze Design Components

Identify all implementation needs:
- Data models and validation
- Services and business logic
- API endpoints and handlers
- UI components
- Tests for each layer
- Integration points

### Step 2: Identify Dependencies

Map what needs to be built first:
- **Technical:** Code dependencies (models before services)
- **Logical:** Feature dependencies (login before profile)
- **Data:** What data must exist first

### Step 3: Sequence Tasks

Order tasks to:
- Respect dependencies
- Enable early validation
- Allow incremental testing
- Minimize blocking between tasks

### Step 4: Write Task Descriptions

For each task, specify:
```markdown
- [ ] X.Y [Task Title]
  - [What to implement]
  - [Files to create/modify]
  - [Key functionality]
  - [Tests to write]
  - _Requirements: [Req-1, Req-2]_
```

## Sequencing Strategi