tech-debt-register

What problem does it solve?

Unstructured, ad-hoc tech debt tracking leads to missed critical issues, unplanned work, and unclear prioritization across development sprints, wasting team time and increasing project risk.

Core Features & Use Cases

• Structured Entry Templates: Supports both detailed 5-field entries for comprehensive audits (with location, root cause, fix plan, effort estimate, and linked references) and simple table formats for quick backlog tracking.
• End-to-End Debt Management Workflows: Built-in guidance for sprint planning, debt closure, progress tracking, and cross-referencing with QA trackers and regression guard entries to align with project standards.
• Edge Case Handling: Includes specialized templates for environment-only tech debt, partial fixes, and deferred items to preserve full historical context for auditors and future team members. A common use case: A development team can use this skill to log a P0 security-related tech debt found during a code review, assign it to the current sprint, track its fix progress, and link it to related regression test entries to prevent the issue from reoccurring.

Quick Start

Use the tech-debt-register skill to log a newly discovered tech debt item from your latest code review, assign it a P0/P1/P2 priority, and add it to your project's tech debt register.