skills.rest
aj-geddes
aj-geddesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

technical-debt

Classify, track, and prioritize technical debt items with structured formats.

14|7|Updated Dec 4, 2025
Search Tags:#refactoring#code-quality#risk-management#technical-debt#debt-tracking
One-click install
npx skills add https://github.com/aj-geddes/unicorn-team --skill technical-debt-aj-geddes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-debt
Source: https://github.com/aj-geddes/unicorn-team/tree/main/skills/technical-debt
Command: npx skills add https://github.com/aj-geddes/unicorn-team --skill technical-debt-aj-geddes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps engineering teams recognize, document, and prioritize technical debt to improve long-term velocity and code quality.

Core Features & Use Cases

  • Debt recognition: identify shortcuts, missing tests, and suboptimal designs at the source.
  • Tracking & prioritization: assign IDs, locations, impacts, and paydown plans to keep debt visible.
  • Workflow integration: link debt items to sprints and code reviews to guide paydown decisions with measurable outcomes.

Quick Start

Log a debt item by file and line, describe the issue, and record a payoff plan.

Frequently Asked Questions about technical-debt

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

FAQPage Schema
How do I track technical debt in my codebase?▼

Track technical debt by logging each item with a structured format that includes file location, description, impact, payoff plan, and status. This enforces visibility and allows development teams to prioritize debt items across repositories.

What's the best way to prioritize technical debt paydown across multiple projects?▼

Prioritize technical debt by assigning IDs and documenting the impact of each item. Structured tracking links debt items to sprints and code reviews, guiding paydown decisions with measurable outcomes across projects.

How do I document code shortcuts and missing tests for future refactoring?▼

Document code shortcuts and missing tests by logging a debt item at the source file and line. Describe the suboptimal design or missing test, then record a specific payoff plan to keep the refactoring goal visible.

Can I use inline TODO markers for technical debt traceability?▼

Yes, the technical debt tracking process supports inline TODO markers. These markers provide traceability directly in the source code, linking the exact location of the shortcut to the structured debt item record.

When do I need a structured format for managing technical debt?▼

A structured format for managing technical debt is needed when teams accumulate shortcuts or suboptimal designs that impact long-term velocity. It enforces documenting the location, impact, and payoff plan to improve code quality.

Does technical debt tracking work across different architectures and repositories?▼

Yes, technical debt tracking is applicable to development teams across architectures, projects, and repositories. It provides a standardized format to document and manage debt items regardless of the underlying system design.

Related Skills

Explore More Software Engineering Skills→
XinAlohaXinAloha
3

ponytail-debt

Scan source files for ponytail comments and generate a debt ledger.

Community
Basic
JeremyDev87JeremyDev87
31

tech-debt

Identify, prioritize, and plan technical debt resolution with ROI-based paydown steps.

Community
Advanced
OmexITOmexIT
13

tech-debt-assessment

Identifies, inventories and prioritizes technical debt across code, architecture, testing, infra, and docs to produce a repayment roadmap with ownership and timelines.

Community
Advanced
Ethical-AI-SyndicateEthical-AI-Syndicate
1

technical-debt-cataloger

Document, prioritize, and plan remediation for technical debt across software projects.

Official
Advanced