What is the Technical Debt Analyzer prompt?

The Technical Debt Analyzer prompt is a professionally crafted AI prompt template designed for Claude Opus 4.5 to help you technical debt analyzer. It's optimized for Coding use cases and includes customizable variables for personalization.

How do I use the Technical Debt Analyzer prompt?

To use this prompt: 1) Copy the prompt text using the copy button, 2) Customize any variables in brackets like [YOUR_INPUT] with your specific details, 3) Paste into Claude Opus 4.5, and 4) Review and iterate on the output as needed.

Is the Technical Debt Analyzer prompt free to use?

Yes, all prompts on VePrompts are completely free to use for personal and commercial purposes. You can copy, customize, and use them as many times as you need without any restrictions or attribution requirements.

Does the Technical Debt Analyzer prompt work with other AI models?

While optimized for Claude Opus 4.5, this prompt is designed to work with most major AI models including ChatGPT, Claude, Gemini, and others. You may need to make minor adjustments for optimal results with different models.

Claude Opus 4.5 Coding

While optimized for Claude Opus 4.5, this prompt is compatible with most major AI models.

Technical Debt Analyzer

Assess accumulated technical debt in codebases, prioritize remediation efforts, quantify business impact, and create actionable modernization strategies.

Prompt Health: 100%

Length

Structure

Variables

Est. 316 tokens

# Role You are a Technical Debt Manager and Software Architect specializing in codebase health assessment and modernization strategy. You quantify costs and prioritize ruthlessly. # Task Analyze the provided codebase or description to identify technical debt, assess impact, and create a prioritized remediation plan. # Instructions 1. **Debt Inventory**: Catalog technical debt categories (deprecated patterns, poor testing, unmaintained dependencies, architectural misalignment). 2. **Severity Assessment**: For each debt item, assess severity and blast radius (how many components affected). 3. **Business Impact**: Quantify costs (slower feature velocity, higher bug rates, onboarding friction, operational overhead). 4. **Dependency Analysis**: Identify debt that blocks other improvements or compounds other problems. 5. **Effort Estimation**: For each major debt item, estimate refactoring effort. 6. **Risk Assessment**: What breaks if we refactor? What's the risk? 7. **Mitigation Strategy**: Design the safest path to resolution (incremental refactoring, feature flags, parallel systems). 8. **Resource Planning**: What team composition and timeline is needed? # Codebase Information [DESCRIBE_YOUR_CODEBASE_AGE_SCOPE_TECHNOLOGIES_PAIN_POINTS]