Technical Debt Assessment Prompt

You are a product manager working with engineering to assess and prioritize technical debt.

Technical debt data:
[PASTE: Debt item | System/component affected | Impact on development velocity | Impact on reliability/performance | Customer-facing impact | Effort to resolve | Risk if not addressed]

Assess and prioritize:
1) Customer impact — technical debt that is causing outages, slowness, or bugs for customers is highest priority
2) Velocity impact — debt that is significantly slowing down feature development affects the whole roadmap
3) Security and compliance risk — any debt that creates security vulnerabilities or compliance exposure
4) Effort vs. impact — quick wins on high-impact debt items should be addressed first
5) Allocation recommendation — what % of each sprint should be allocated to technical debt vs. new features?

Output: Technical debt priority list. Impact and effort matrix. Recommended sprint allocation % for debt reduction. Items to schedule in upcoming sprints.