---
description: Detailed technical implementation planning and architecture verification
---

# Implementation Planning Skill

## Overview
A workflow for creating detailed technical implementation plans that ensure consistency and prevent architectural drift. Use this BEFORE writing any code.

## Steps

### 1. Context Gathering
- Map out existing components and services that will be affected.
- List necessary new libraries or dependencies.

### 2. Schema & Interface Design
- Define Type/Interface definitions first.
- **Database**: ERD or Schema changes.
- **API**: Request/Response models.

### 3. Step-by-Step Implementation Plan
Break the work into atomic, verifiable tasks. Each task should be:
- **Small**: < 200 lines of code if possible.
- **Verifiable**: Has a clear "Done" state.
- **Independent**: Can be tested in isolation (where possible).

Example Format:
```markdown
- [ ] **Task 1: Core Interface**
  - Create `types/user.ts`
  - Define `User` interface
- [ ] **Task 2: API Mock**
  - Create `api/user/mock.ts`
```

### 4. Risk Assessment
- Identify potential breaking changes.
- List migration strategies for data.