Managing Tech Debt

This compiles tactical advice from 18 product leaders on handling tech debt without falling into the rewrite trap. Use it when you're trying to decide between incremental fixes and starting over, when you need to quantify the business cost of debt to get stakeholder buy-in, or when your team is stuck firefighting instead of shipping. The most useful bit is probably the reframe that tech debt is product debt, not just engineering's problem. It pushes hard against full rewrites (Camille Fournier's warning about underestimating migration time is worth the price alone) and includes specific tactics like Delete Code Clubs and refusing to maintain bug backlogs. Best for teams past the scrappy MVP stage who are feeling the friction.

Install to Claude Code

npx -y skills add refoundai/lenny-skills --skill managing-tech-debt --agent claude-code