skills.rest
jerelvelarde
jerelvelardeCOMMUNITY
Explore all skills by this author →
GitHub

manage-tech-debt

Track and prioritize technical debt in a codebase register.

6|Updated Feb 19, 2026
Search Tags:#code quality#planning#prioritization#tech debt#register#engineering governance
One-click install
npx skills add https://github.com/jerelvelarde/chalk-skills --skill manage-tech-debt-jerelvelarde
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-tech-debt
Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/manage-tech-debt
Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill manage-tech-debt-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track, categorize, and prioritize technical debt when the user asks to manage tech debt, create a tech debt register, assess code quality, or plan refactoring work.

Core Features & Use Cases

  • Maintain a living Tech Debt Register at .chalk/docs/engineering/tech_debt_register.md, supporting classification by Category and Quadrant.
  • Read project context (architecture docs, ADRs/RFCs, upcoming roadmaps) and: Add, Assess, Prioritize, Review, or Retire debt items with fields (Category, Quadrant, Description, Location, Impact, Payoff, Business Justification, Strategic Alignment).
  • Summarize top priorities and align debt work with upcoming initiatives.

Quick Start

To start, read the engineering context and update the tech debt register with any new items for the current sprint.

Frequently Asked Questions about manage-tech-debt

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

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

A technical debt register is a living document that tracks categorized debt items by quadrant, impact, and payoff. It helps engineering teams systematically identify, assess, and prioritize refactoring work alongside upcoming roadmap initiatives.

What fields should a technical debt register include for engineering governance?▼

A technical debt register should include Category, Quadrant, Description, Location, Impact, Payoff, Business Justification, and Strategic Alignment fields. These fields ensure debt items are properly assessed and aligned with project roadmaps for effective prioritization.

How do I align technical debt resolution with upcoming project roadmaps?▼

Align technical debt resolution by reading project context, architecture docs, and ADRs alongside upcoming roadmaps to assess and prioritize items. This ensures debt work is strategically aligned with planned business initiatives and sprint goals.

What's the best way to categorize technical debt for prioritization?▼

The best way to categorize technical debt is by using a quadrant system alongside impact and payoff fields. This categorization allows teams to systematically prioritize refactoring efforts based on business justification and strategic alignment.

When should I review or retire items from my tech debt register?▼

Review or retire tech debt register items during ongoing engineering projects when assessing current sprint priorities. Regularly update the register by reading project context to ensure resolved debt items are retired and new ones are added.

Related Skills

Explore More Software Engineering Skills→
viditparashar96viditparashar96

eng-tech-debt

Catalog tech debt items, score business impact, and generate prioritized payoff plans.

Community
Intermediate
FoundationForgeFoundationForge

tech-debt

Identify, categorize, and prioritize technical debt across a codebase.

Official
Intermediate
GeneralJerelGeneralJerel
6

manage-tech-debt

Track, categorize, and prioritize technical debt in a structured register.

Community
Advanced
solace-illsolace-ill

tech-debt

Scan codebases for TODO, FIXME, HACK, and deprecated markers to categorize and prioritize technical debt.

Community
Advanced