skills.rest
adrianliechti
adrianliechtiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tech-debt

Identify, categorize, and prioritize technical debt across codebases and systems.

4|4|Updated Dec 15, 2024
Search Tags:#architecture#refactoring#remediation#code-quality#risk-analysis#tech-debt#backlog-prioritization
One-click install
npx skills add https://github.com/adrianliechti/wingman-chat --skill tech-debt-adrianliechti
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-debt
Source: https://github.com/adrianliechti/wingman-chat/tree/main/skills/engineering/tech-debt
Command: npx skills add https://github.com/adrianliechti/wingman-chat --skill tech-debt-adrianliechti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify, categorize, and prioritize technical debt across codebases and architectures to prevent escalation and slowdowns.

Core Features & Use Cases

  • Debt identification: Scan codebases for duplicated logic, architectural debt, and test debt.
  • Prioritization framework: Apply Impact, Risk, and Effort scoring to rank debt items.
  • Remediation planning: Generate a phased plan aligned with ongoing feature work.

Quick Start

Run a tech debt audit across the repository to identify, categorize, and prioritize issues and outline a phased remediation plan.

Frequently Asked Questions about tech-debt

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

FAQPage Schema
How do I prioritize technical debt in my software backlog?▼

You prioritize technical debt by applying an Impact, Risk, and Effort scoring framework to rank items. This generates a prioritized list with estimated effort, business justification, and a phased remediation plan aligned with ongoing feature work.

What types of technical debt can I identify across a codebase?▼

You can identify technical debt across code, configuration, and infrastructure. The audit specifically scans for duplicated logic, architectural debt, and test debt to categorize issues and prevent escalation and delivery slowdowns.

How do I create a phased remediation plan for architectural debt?▼

Creating a phased remediation plan for architectural debt involves identifying and categorizing issues during architecture reviews, then generating a prioritized list with estimated effort and business justification aligned with ongoing maintenance tasks.

When should I conduct a technical debt audit during the development lifecycle?▼

A technical debt audit should be conducted during backlog grooming, architecture reviews, and ongoing maintenance tasks. Running the audit at these stages helps identify, categorize, and prioritize issues to prevent delivery slowdowns.

How do I justify technical debt remediation to business stakeholders?▼

Justifying technical debt remediation requires generating a prioritized list that includes business justification alongside estimated effort. This approach connects debt remediation directly to preventing escalation and speeding up feature delivery.

Related Skills

Explore More Software Engineering Skills→
nikhillinitnikhillinit

tech-debt-tracker

Detect and prioritize technical debt with configurable thresholds and SQALE metrics.

Community
Advanced
ilove323ilove323

tech-debt

Identify and prioritize technical debt using impact, risk, and effort scoring.

Community
Advanced
li3pli3p

debt-scan

Identify and prioritize technical debt in a codebase for remediation planning.

Community
Intermediate
amanhsnamanhsn

Tech Debt Tracker

Scan codebases to identify, quantify, and prioritize technical debt.

Community
Advanced