Implementation Planning

When to Use

Use when:

• You have a feature spec in /docs/features/ and are ready to implement
• You need to break a complex feature into manageable phases
• You want a TDD-focused implementation roadmap

Don't use when:

• Feature requirements aren't clear yet (use feature-discovery first)
• Feature is trivial (< 3 tasks total)

Process

1. Analyze Feature Specification

• Read the feature spec from /docs/features/[feature-name].md
• Extract requirements and acceptance criteria
• Identify complexity areas and risks
• Review codebase for integration points

2. Design Phase Breakdown

• Identify vertical slices (end-to-end capabilities)
• Sequence for value delivery (testable functionality earliest)
• Size appropriately (30-90 min per task)
• Define deliverables for each phase

3. Create Implementation Tasks

For each phase, define:

• Phase Goal: One sentence describing what this phase accomplishes
• RED tasks: Tests to write first
• GREEN tasks: Code to make tests pass
• REFACTOR tasks: Cleanup and improvements
• Acceptance Criteria: How to verify completion

4. Generate Output

• Write plan to /docs/implementation/[feature-name]-implementation-plan.md
• Populate TodoWrite with Phase 1 tasks only
• Add subsequent phases as each completes

Core Principles

TDD Vertical Slices

• Test-First: Write tests before implementation
• End-to-End: Each phase delivers working functionality
• Incremental: Build on previous phases

Appropriate Sizing

• 30-90 minutes per task
• Concrete acceptance criteria
• Independently testable

See TASKSIZINGGUIDE.md for detailed guidance.

Risk-Aware Sequencing

• Validate assumptions early (high-risk items first)
• Build foundation first (core models before complex logic)
• Enable testing at each step

Phase Template

### Phase N: [Descriptive Name]
**Goal**: [One sentence describing what this phase delivers]

**Vertical Slice**: [What end-to-end capability does this deliver?]

#### RED - Write Failing Tests
- [ ] Test: [Specific test case]
- [ ] Test: [Edge case]

#### GREEN - Make Tests Pass
- [ ] Create/modify: [File or class]
- [ ] Implement: [Method or functionality]

#### REFACTOR - Clean Up
- [ ] Extract: [What to pull out]
- [ ] Remove: [Duplication to eliminate]

**Acceptance Criteria**:
- [ ] All tests pass
- [ ] [Observable behavior works]

**Deliverable**: [Working functionality that can be demonstrated]

Output

Implementation Plan Document

/docs/implementation/[feature-name]-implementation-plan.md

• Phase breakdown with tasks
• Testing strategy
• Files to create/modify
• Risk mitigation

Use IMPLEMENTATION_TEMPLATE.md as a starting point.

TodoWrite Task List

• Populated with Phase 1 tasks only
• Ready to start implementing immediately
• Next phases added as you progress

Workflow

feature-discovery → plan-implementation → implement phases → repeat
       ↓                    ↓                    ↓
  Feature Spec      Implementation Plan    Working Code

Phase Progression (CRITICAL)

STOP after each phase for user review and approval before proceeding.

1. Implement Phase N
2. Run tests to verify
3. Report results to user
4. STOP and WAIT for user review
5. User approves → Commit changes
6. User confirms → Start Phase N+1

DO NOT proceed to the next phase without explicit user approval.

Each phase checkpoint should include:

• Summary of what was implemented
• Test results (all tests passing)
• Files created/modified
• Ask: "Would you like me to commit these changes?"
• Wait for approval before committing
• Wait for approval before starting the next phase

Reference Files

• QUICK_START.md: Fast reference for getting started
• TASKSIZINGGUIDE.md: How to size tasks appropriately
• IMPLEMENTATION_TEMPLATE.md: Template for output documents

Tools Used

• Read, Grep, Glob to analyze specs and codebase
• TodoWrite to create task list
• AskUserQuestion to clarify implementation choices