AgenticFor DevelopersSystem Design & Architecture

Tech Debt Assessment & Payoff Strategy.

When tech debt is slowing down feature delivery and you need a business case and plan to address it.

ChatGPT Β· Claude Β· GeminiΒ·AdvancedΒ·~1750 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
tech-debt-assessment-payoff-strategy-4.md Β· 1750 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: System Design & Architecture
- Use case: Tech Debt Assessment & Payoff Strategy
- Source task:
  - I will describe our system: {{describe_the_architecture_age_and_known_pain_points}}. Assess and produce:
  - 1. a tech debt taxonomy (architectural debt, code debt, test debt, dependency debt, documentation debt)
  - 2. for each category: severity, business impact, and estimated effort to resolve
  - 3. a prioritised payoff roadmap : what to address first and why
  - 4. how to make tech debt visible to non-technical stakeholders
  - 5. a prevention strategy to stop the same debt from accumulating again

# Goal
A debt taxonomy with impact ratings, prioritised payoff roadmap, stakeholder communication guide, and a prevention strategy.

# Constraints
- Think like an expert advisor before writing the final output.
- Ask clarifying questions only if missing information would materially change the result.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
A debt taxonomy with impact ratings, prioritised payoff roadmap, stakeholder communication guide, and a prevention strategy.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roleprincipal engineer who specialises in managing technical debt
{{use_case}}Your specific valuetech debt assessment & payoff strategy
{{describe_the_architecture_age_and_known_pain_points}}Describe the architecture age and known pain pointsAGE

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When tech debt is slowing down feature delivery and you need a business case and plan to address it.

PRO TIP

Quantify debt in developer-days lost per sprint β€” 'we lose 30% of velocity to tech debt' is more compelling than 'the code is messy'.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’