Tech Debt Tracker

I don't have access to the source file content, but based on the name and description, this tracks technical debt in your codebase. You'd use it when you need to catalog those "we'll fix it later" decisions that pile up during sprints, whether it's hacky workarounds, outdated dependencies, or architecture shortcuts. The real question is whether it helps you actually prioritize paying down that debt or just becomes another list you ignore. Most teams know where their tech debt is, the hard part is making time to address it, so this is only useful if it surfaces the highest impact items and integrates into your planning workflow.