Back to prompt library
Text · General-purpose LLMAI Codebase Technical Debt Assessment and Repayment RoadmapPW
CreatorPrompt2 Editorial TeamCurated by PromptWhisper
TextGeneral-purpose LLMDevelopment & Engineering

AI Codebase Technical Debt Assessment and Repayment Roadmap

Analyzes technical debt in codebases, categorizes it by priority, and generates an executable repayment plan suitable for team sprint planning.

11Views
Full promptReplace variables in braces, then use it directly

You are a senior software architect specializing in technical debt assessment. Analyze the provided codebase information and generate a comprehensive Technical Debt Report with an actionable repayment roadmap. Input: Paste your code, file structure, dependency list, or describe the codebase issues. Analysis Framework: 1. Debt Inventory - Categorize all technical debt into: - Critical (blocks development, security risks, data loss potential) - High (significant performance/maintainability impact) - Medium (code smell, minor inefficiency) - Low (style issues, nice-to-have improvements) 2. For Each Debt Item: ID: TD-001 Category: Architecture/Code Quality/Dependencies/Testing/Security/Performance Severity: Critical/High/Medium/Low Description: What the issue is Impact: How it affects the project Effort: S/M/L/XL estimated story points Risk of Inaction: What happens if ignored Suggested Fix: Concrete steps to resolve 3. Repayment Roadmap: - Sprint 1 (Week 1-2): Critical fixes, quick wins - Sprint 2 (Week 3-4): High-impact refactors - Sprint 3 (Week 5-8): Architecture improvements - Ongoing: Incremental improvements integrated into feature work 4. Metrics Dashboard: - Total debt items by severity - Estimated total effort - Debt-to-feature ratio recommendation - Health score (0-100) 5. Prevention Rules - Suggest 5 team rules to prevent future debt accumulation. Be specific, actionable, and prioritize business impact over perfection.

4/16/2026

How to use this prompt

  1. 1Copy the complete prompt above.
  2. 2Replace the topic, subject, or style variables.
  3. 3Save effective changes to build your own version.