Produce a Tech Debt Management Pack in Markdown (in-chat; or as files if requested):
1) Context snapshot (scope, pains, constraints, stakeholders, success definition) 2) Tech Debt Register (inventory table with owners, symptoms, impact, effort range, risks) 3) Scoring + prioritization (model + ranked list + rationale) 4) Strategy decision(s) (refactor/migrate/rebuild/deprecate) with explicit criteria
5) Execution plan (incremental milestones, sequencing, resourcing, decommission plan) 6) Migration + rollback plan (if applicable; includes “dual-run” cost/plan) 7) Metrics plan (baseline, targets, leading indicators, instrumentation gaps, small tests) 8) Risks / Open questions / Next steps (always included)
Manage technical debt by producing a Tech Debt Management Pack (debt register, scoring/prioritization, refactor vs rewrite decision memo, incremental paydown plan, migration/rollback plan, metrics, and stakeholder cadence). Use for tech debt, refactoring, legacy modernization, and migrations. Source: liqiongyu/lenny_skills_plus.