tech-debt

Scan codebases for debt indicators and generate a prioritized debt register.

3|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill tech-debt-negentropy-laby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/tech-debt
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill tech-debt-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track and manage technical debt across a codebase, enabling teams to surface, categorize, and schedule repayment.

Core Features & Use Cases

  • Debt discovery: scan for indicators like TODO, FIXME, and anti-patterns to surface debt.
  • Debrief and register: maintain a living debt register with categories and priorities.
  • Planning and execution: prioritize fixes and plan work for sprints or releases.

Quick Start

Scan the repository for debt indicators and generate a prioritized debt register for your next sprint.

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 a codebase?

To track and prioritize technical debt, you can scan the codebase for indicators like TODO and FIXME to automatically surface, categorize, and register debt. This generates a prioritized debt register to inform sprint planning and remediation decisions.

What is a technical debt register and how does it help sprint planning?

A technical debt register is a living catalog that classifies debt into architecture, code quality, test, and documentation categories. It links evidence to each entry, enabling teams to prioritize fixes and schedule repayment work for upcoming sprints or releases.

How do I scan my codebase for TODO and FIXME anti-patterns?

You can scan a codebase for debt indicators like TODO, FIXME, and anti-patterns to automatically discover and catalog technical debt. The process routes identified debt into specific categories and requires user approval before writing to project artifacts.

Can I automatically categorize technical debt by architecture or code quality?

Yes, technical debt can be automatically categorized by applying domain routing to classify entries into architecture, code quality, test, and documentation categories. Each entry is linked to evidence to support prioritization and remediation planning.

Does cataloging technical debt require manual approval before writing to project artifacts?

Yes, cataloging technical debt enforces guardrails by requiring user approval before making any writes to the memory bank or project artifacts. This ensures evidence is linked to each debt entry and prevents unauthorized modifications.