tech-debt-tracker

Detect and manage technical debt from conversations and PR reviews into a structured backlog.

12.6k|1.5k|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/nearai/ironclaw --skill tech-debt-tracker-nearai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-debt-tracker
Source: https://github.com/nearai/ironclaw/tree/main/skills/tech-debt-tracker
Command: npx skills add https://github.com/nearai/ironclaw --skill tech-debt-tracker-nearai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams identify technical debt mentioned in day-to-day conversations and PR reviews, so that temporary shortcuts and refactors don’t get forgotten and resurface at the right time for action.

Core Features & Use Cases

  • Detects tech debt from language patterns: Extracts items from prompts like hacks, workarounds, TODOs, or “should refactor later” statements.
  • Scans PR review comments for follow-up debt: Converts review feedback indicating non-blocking issues into trackable debt entries.
  • Manages the full lifecycle: Lists a backlog, resolves items, and promotes selected debt into open commitments for follow-up work.

Quick Start

Use the tech-debt-tracker skill to add a new item by saying: add tech debt: the caching layer needs TTL eviction.

Frequently Asked Questions about tech-debt-tracker

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

FAQPage Schema
How do I track technical debt mentioned in pull request reviews?

Track technical debt from PR reviews by scanning comments for non-blocking issues and converting that feedback into structured backlog entries with severity, category, and source metadata.

What is the best way to capture workarounds and TODOs from developer conversations?

Capture workarounds and TODOs from conversations by detecting language patterns like hacks or 'should refactor later' statements, then writing them as durable items into a structured technical debt backlog.

Can I promote backlog items into commitments for sprint planning?

Yes, you can promote backlog items into open commitments during triage workflows, moving selected technical debt entries into actionable follow-up work for your development cycle.

How do I manage the lifecycle of refactoring tasks during weekly retrospectives?

Manage refactoring tasks during weekly retrospectives by listing the existing technical debt backlog, resolving completed items, and promoting remaining entries into commitments for future resolution.

Does the technical debt tracker prevent duplicate entries in the backlog?

Yes, the tracker applies pattern-based de-duplication when detecting technical debt items, ensuring that identical workarounds or TODOs mentioned across multiple conversations do not create duplicate backlog entries.