tech-debt

Scan codebases for debt indicators and generate prioritized repayment plans.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/packetalien/cursor-game-studios --skill tech-debt-packetalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/packetalien/cursor-game-studios/tree/main/.cursor/skills/tech-debt
Command: npx skills add https://github.com/packetalien/cursor-game-studios --skill tech-debt-packetalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track and prioritize technical debt across a codebase.

Core Features & Use Cases

  • Debt scanning and categorization to surface areas of risk and complexity.
  • Maintains a centralized debt register with status, priority, and suggested repayment timelines.
  • Supports a phased workflow from discovery through remediation, including sprint-planning alignment.

Quick Start

Run the tech-debt workflow to scan the repository for debt indicators and generate a prioritized repayment plan.

Frequently Asked Questions about tech-debt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track and prioritize technical debt across my codebase?

To track technical debt, scan your codebase for debt indicators to categorize risk and complexity. This generates a centralized debt register with status and priority for repayment scheduling.

How does tech debt scanning align with sprint planning?

Tech debt scanning aligns with sprint planning by recommending repayment timelines based on discovered debt indicators. It supports a phased workflow from discovery to remediation, allowing teams to schedule debt repayment alongside feature development.

Can I use this tech debt tracker for software projects of any size?

Yes, this tech debt tracker targets software projects of any size. It scans for debt indicators across the entire codebase and maintains a centralized register regardless of project scale.

What is the best way to categorize code complexity and risk for refactoring?

The best way to categorize code complexity and risk is through debt scanning and categorization. This surfaces areas of risk and complexity in your code, maintained in a register to guide refactoring priorities.

What is included in a centralized debt register for code quality management?

A centralized debt register for code quality management includes the status, priority, and suggested repayment timelines for each identified debt item. It serves as the core tracking mechanism from discovery to remediation.