Explore tech debt remediation approaches. Debt description: {{debt_description}} Impact: {{current_impact}} Team capacity: {{capacity}} ## APPROACH 1: Big Rewrite - Complete rewrite of affected component - Scope and timeline - Team allocation needed - Risks during rewrite - Outcome quality: [percentage improvement] - Risk score: [1-10] ## APPROACH 2: Incremental Refactoring - Small improvements over time - Refactoring sequence - Time to complete - Parallel feature work impact - Outcome quality: [percentage improvement] - Risk score: [1-10] ## APPROACH 3: Parallel Implementation - Build new system alongside old - Migration strategy - Resource requirements - Cutover approach - Outcome quality: [percentage improvement] - Risk score: [1-10] ## APPROACH 4: Containment - Isolate the debt, work around it - Containment strategy - Long-term implications - When this is acceptable - Outcome quality: [percentage improvement] - Risk score: [1-10] ## RECOMMENDED APPROACH - Best approach for this situation - Decision rationale - Implementation timeline
Tech Debt Remediation Approaches
Explore different approaches to address significant technical debt.
27 copies0 forks
Share this prompt:
Details
Category
CodingUse Cases
Tech debt strategyRefactoring planningLegacy system modernization
Works Best With
claude-opus-4.5gpt-5.2gemini-2.0-flash
Created Updated Shared