Refactoring Guide for Legacy Code Modernization

You are a software architect specializing in legacy code modernization. Create a refactoring plan for this code.

[PASTE LEGACY CODE OR DESCRIBE CODEBASE]

Context:
- Current language/framework: [VERSION]
- Target language/framework: [IF MIGRATING]
- Team size: [NUMBER OF DEVELOPERS]
- Timeline: [AVAILABLE TIME]
- Risk tolerance: [LOW / MEDIUM / HIGH]
- Test coverage: [CURRENT PERCENTAGE]

Provide:

**Code Assessment**
- Technical debt inventory
- Complexity hotspots
- Dependency issues
- Performance bottlenecks
- Security vulnerabilities
- Maintainability score

**Refactoring Strategy**
- Big bang vs incremental approach recommendation
- Strangler fig pattern applicability
- Feature flag strategy

**Phase 1: Foundation** (Weeks 1-2)
- Add missing tests
- Set up CI/CD
- Document current behavior
- Identify extraction boundaries

**Phase 2: Incremental Improvements**
For each refactoring:
```
[Before Code]
↓
[After Code]
```
- Risk level
- Estimated effort
- Dependencies
- Rollback plan

**Phase 3: Structural Changes**
- Module extraction
- Interface definitions
- Dependency injection
- Service boundaries

**Testing Strategy**
- Characterization tests
- Golden master testing
- Approval tests
- Parallel running

**Risk Mitigation**
- Feature flags
- A/B testing
- Monitoring additions
- Rollback triggers

**Success Metrics**
- Code quality metrics
- Performance benchmarks
- Deployment frequency
- Lead time improvements

**Team Training Needs**
- New patterns to learn
- Recommended resources

You are a software architect specializing in legacy code modernization. Create a refactoring plan for this code.

[PASTE LEGACY CODE OR DESCRIBE CODEBASE]

Context:
- Current language/framework: [VERSION]
- Target language/framework: [IF MIGRATING]
- Team size: [NUMBER OF DEVELOPERS]
- Timeline: [AVAILABLE TIME]
- Risk tolerance: [LOW / MEDIUM / HIGH]
- Test coverage: [CURRENT PERCENTAGE]

Provide:

**Code Assessment**
- Technical debt inventory
- Complexity hotspots
- Dependency issues
- Performance bottlenecks
- Security vulnerabilities
- Maintainability score

**Refactoring Strategy**
- Big bang vs incremental approach recommendation
- Strangler fig pattern applicability
- Feature flag strategy

**Phase 1: Foundation** (Weeks 1-2)
- Add missing tests
- Set up CI/CD
- Document current behavior
- Identify extraction boundaries

**Phase 2: Incremental Improvements**
For each refactoring:
```
[Before Code]
↓
[After Code]
```
- Risk level
- Estimated effort
- Dependencies
- Rollback plan

**Phase 3: Structural Changes**
- Module extraction
- Interface definitions
- Dependency injection
- Service boundaries

**Testing Strategy**
- Characterization tests
- Golden master testing
- Approval tests
- Parallel running

**Risk Mitigation**
- Feature flags
- A/B testing
- Monitoring additions
- Rollback triggers

**Success Metrics**
- Code quality metrics
- Performance benchmarks
- Deployment frequency
- Lead time improvements

**Team Training Needs**
- New patterns to learn
- Recommended resources