Product Technical Debt Strategy

## ROLE
You are a technical strategy expert who helps product teams balance innovation with technical health.

## CONTEXT
I need to develop a strategy for managing technical debt that allows us to maintain product velocity while improving our technical foundation.

## TASK
Create a comprehensive technical debt strategy:

**DEBT INVENTORY**
- Catalog existing technical debt
- Categorize by type:
  - Code debt
  - Architecture debt
  - Test debt
  - Documentation debt
  - Dependency debt
- Quantify impact of each

**DEBT ASSESSMENT**
For each major debt item:
- Description
- Root cause
- Impact on development
- Impact on users
- Risk level
- Interest rate (growing vs stable)

**PRIORITIZATION FRAMEWORK**
- Impact on velocity
- Impact on quality
- Impact on security
- Remediation effort
- Priority score

**INVESTMENT STRATEGY**
- Debt budget (% of capacity)
- When to pay down debt
- When to incur new debt
- Debt ceiling thresholds

**REMEDIATION ROADMAP**
*Quick Wins (1-2 weeks):*
- Items to address
- Expected benefit

*Medium-term (1-3 months):*
- Items to address
- Expected benefit

*Long-term (3-12 months):*
- Items to address
- Expected benefit

**PREVENTION STRATEGIES**
- Code review standards
- Architecture review gates
- Testing requirements
- Documentation standards
- Definition of done updates

**TRACKING & REPORTING**
- How to track debt
- Metrics to monitor
- Reporting cadence
- Stakeholder communication

**TEAM ALIGNMENT**
- Engineering buy-in
- PM/business alignment
- Communicating debt to stakeholders
- Making debt visible

## INPUT
Product: {{PRODUCT}}
Known Debt: {{KNOWN_DEBT}}
Team Size: {{TEAM}}
Current Velocity: {{VELOCITY}}
Pain Points: {{PAIN_POINTS}}