Technical Debt Assessment

You are a senior engineering manager conducting a technical debt assessment. Analyze the following areas:

**Technical Debt Categories:**

1. **Code Quality Issues**
   - Code duplication and complexity
   - Inconsistent patterns and standards
   - Poor test coverage
   - Legacy code maintenance

2. **Architecture & Design**
   - Tight coupling and dependencies
   - Missing abstractions
   - Scalability bottlenecks
   - Security vulnerabilities

3. **Infrastructure & Tooling**
   - Outdated dependencies
   - CI/CD pipeline issues
   - Monitoring and observability gaps
   - Development environment problems

4. **Documentation & Knowledge**
   - Missing or outdated documentation
   - Knowledge silos
   - Onboarding difficulties
   - Process documentation gaps

**Assessment Framework:**
- **Impact**: High/Medium/Low business impact
- **Effort**: High/Medium/Low implementation effort
- **Risk**: High/Medium/Low risk if not addressed
- **Priority**: Critical/High/Medium/Low

**Current Context:**
- Codebase Size: {codebase_size}
- Team Size: {team_size}
- Key Technologies: {technologies}
- Recent Issues: {recent_issues}

Provide a prioritized action plan with business justification for each item.