skills.rest
14790897
14790897COMMUNITY
Explore all skills by this author →
Website𝕏@hahfrankGitHub

kwp-engineering-tech-debt

Categorize and prioritize technical debt using an Impact, Risk, and Effort formula.

7|5|Updated May 7, 2026
Search Tags:#code quality#refactoring#audit#maintenance#technical debt#engineering
One-click install
npx skills add https://github.com/14790897/MiQi --skill kwp-engineering-tech-debt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kwp-engineering-tech-debt
Source: https://github.com/14790897/MiQi/tree/main/miqi/skills/kwp/engineering/tech-debt
Command: npx skills add https://github.com/14790897/MiQi --skill kwp-engineering-tech-debt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the accumulation of unmanaged technical debt that slows down development cycles, increases bug rates, and complicates system maintenance.

Core Features & Use Cases

  • Categorization: Classifies debt into code, architecture, test, dependency, documentation, and infrastructure buckets.
  • Prioritization Framework: Uses a quantitative formula (Impact + Risk) x (6 - Effort) to rank remediation tasks objectively.
  • Use Case: When a team feels overwhelmed by legacy code, use this skill to audit the codebase, identify the highest-risk areas, and generate a phased refactoring plan that balances maintenance with new feature delivery.

Quick Start

Ask the agent to perform a technical debt audit on the current project to identify and prioritize the most critical refactoring tasks.

Frequently Asked Questions about kwp-engineering-tech-debt

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

FAQPage Schema
How do I audit technical debt in a legacy codebase?▼

To audit technical debt, the Skill categorizes issues into code, architecture, test, dependency, and infrastructure buckets, then applies a quantitative formula to rank remediation tasks objectively.

What is the best way to prioritize refactoring tasks alongside feature development?▼

Prioritize refactoring tasks by applying the formula (Impact + Risk) x (6 - Effort) to generate a phased plan that balances code health maintenance with new feature delivery.

How does the technical debt prioritization framework calculate risk?▼

The prioritization framework calculates risk using a quantitative formula combining Impact, Risk, and Effort, scoring remediation tasks to objectively guide refactoring efforts.

Can I categorize infrastructure bottlenecks and documentation debt separately?▼

Yes, the audit classifies technical debt into distinct categories including code, architecture, test, dependency, documentation, and infrastructure bottlenecks for targeted maintenance.

What should I do when unmanaged technical debt slows down development cycles?▼

When unmanaged technical debt slows development, perform a structured codebase audit to identify high-risk areas and generate a phased refactoring plan to improve system maintainability.

Related Skills

Explore More Software Engineering Skills→
silaslopes100silaslopes100

reversa-architect

Generates C4 diagrams, ERD models, and integration maps from project source code.

Community
Advanced
sanskarbasnetsanskarbasnet
1

health

Compute a weighted 0-10 code health score from type checker, linter, test runner, dead code detector, and shell linter.

Community
Intermediate
I-OnlabsI-Onlabs
3

code-auditor

Audit codebases across architecture, quality, security, and performance to produce prioritized health reports.

Community
Advanced
raybargasraybargas

Global Coding Style

Detect and fix coding style violations across multi-language repositories.

Community
Basic