Dev Technical Debt Assessment Report
====================================

Create a technical debt assessment report for [system/codebase].

Assessment details:
- System: [name and description]
- Age: [years]
- Team size: [current]
- Languages/frameworks: [list]
- Test coverage: [%]
- Last major refactor: [date or never]
- Business concern: [slow development/reliability/scaling]

TECHNICAL DEBT ASSESSMENT

1. EXECUTIVE SUMMARY
   - Overall debt level: [Critical/High/Medium/Low]
   - Estimated effort to address: [person-weeks]
   - Business risk if not addressed: [describe]
   - Recommended action: [immediate/planned/monitor]

2. DEBT CATEGORIES

   CODE QUALITY DEBT
   Severity: [High/Medium/Low]
   - Code duplication: [% or description]
   - Complexity score: [if measured]
   - Long methods/classes: [count]
   - Missing tests: [coverage %]
   - Linting violations: [count]
   Impact: [slower development/more bugs]

   ARCHITECTURE DEBT
   Severity: []
   - Monolith that should be modular: [yes/no]
   - Circular dependencies: [count]
   - Tight coupling: [examples]
   - Missing abstraction layers: [describe]
   Impact: [hard to scale/change]

   DEPENDENCY DEBT
   Severity: []
   - Outdated dependencies: [count/major versions behind]
   - EOL dependencies: [list]
   - Security vulnerabilities: [count from audit]
   - Unpinned versions: [risk]
   Impact: [security risk/incompatibility]

   DOCUMENTATION DEBT
   Severity: []
   - Missing README or outdated
   - No API documentation
   - No architecture decision records
   - Tribal knowledge risk
   Impact: [slow onboarding/knowledge loss]

   INFRASTRUCTURE DEBT
   Severity: []
   - Manual deployments: [yes/no]
   - No CI/CD: [yes/no]
   - Missing monitoring: [gaps]
   - Unencrypted data: [yes/no]
   Impact: [reliability/security risk]

3. PRIORITIZED REMEDIATION PLAN

   IMMEDIATE (this sprint)
   - [Item]: [effort] — [reason for urgency]

   SHORT TERM (next quarter)
   - [Item]: [effort] — [impact]

   LONG TERM (roadmap)
   - [Item]: [effort] — [strategic value]

4. PREVENTION STRATEGY
   - Definition of done includes: [no new debt criteria]
   - 20% time rule: [dedicate to debt reduction]
   - Regular debt review: [monthly/quarterly]
   - Automated quality gates: [in CI pipeline]

Source: https://promptzyo.com/prompt/dev-technical-debt-assessment-report