td_fix

Resolve open technical debt items from TECH_DEBT.md with tests.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/wesuuu/runbook --skill td-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: td_fix
Source: https://github.com/wesuuu/runbook/tree/main/.agent/skills/td_fix
Command: npx skills add https://github.com/wesuuu/runbook --skill td-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify, prioritize, and resolve open technical debt items documented in TECH_DEBT.md, reducing project risk and maintenance burden.

Core Features & Use Cases

  • Open-item prioritization: Reviews items by severity and effort to surface high-impact debts.
  • Item-scoped fixes: Allows targeting a specific TD item by ID (e.g., TD-0012) or by severity (e.g., critical) for focused work.
  • End-to-end workflow: Reads TECH_DEBT.md, researches the item, presents a plan, implements changes, updates tests, and marks the item as resolved.

Quick Start

Tell me which TD item to fix by providing an ID (e.g., TD-0012) or a priority (e.g., critical) using /td_fix.

Frequently Asked Questions about td_fix

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

FAQPage Schema
How do I efficiently prioritize and fix technical debt items?

To efficiently fix technical debt, items are prioritized by severity and effort, or targeted by specific IDs. This surfaces high-impact debts for focused, item-scoped resolutions that reduce project maintenance burden.

How do I resolve open tech debt items tracked in a markdown file?

Resolving tech debt items tracked in TECH_DEBT.md involves reading the file, researching the selected item, presenting a plan, implementing changes, running tests, and marking the item as RESOLVED.

Can I fix a specific technical debt item by its ID or severity level?

Yes, you can fix technical debt by providing a specific item ID for targeted work, or by specifying a severity level to automatically pick the highest-severity open item requiring the smallest effort.

What is the end-to-end workflow for resolving technical debt in a codebase?

The end-to-end workflow for resolving technical debt involves researching the item, creating an approval plan, implementing the fix, writing tests, running backend and frontend tests, and updating documentation after tests pass.

How do I ensure my tech debt fixes pass backend and frontend tests?

To ensure tech debt fixes pass tests, the implementation workflow includes writing or updating tests, running both backend and frontend test suites, and only marking the item as resolved after all tests pass successfully.