technical-debt-prioritisation

Score technical debt items across impact, risk, and effort dimensions.

1|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/mcj-coder/development-skills --skill technical-debt-prioritisation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-debt-prioritisation
Source: https://github.com/mcj-coder/development-skills/tree/main/skills/technical-debt-prioritisation
Command: npx skills add https://github.com/mcj-coder/development-skills --skill technical-debt-prioritisation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bc, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of prioritizing technical debt by providing a structured, evidence-based framework, moving beyond subjective opinions or gut feelings.

Core Features & Use Cases

  • Three-Dimensional Scoring: Evaluates debt on Impact, Risk, and Effort.
  • Categorization: Organizes debt by type (e.g., Code Quality, Architecture).
  • Roadmap Planning: Creates multi-horizon plans (sprint, quarterly, 6-month).
  • Use Case: When faced with a backlog of technical debt items, use this Skill to objectively score each item, identify quick wins, and plan a remediation roadmap that aligns with business priorities.

Quick Start

Use the technical-debt-prioritisation skill to score a new debt item with impact 4, risk 3, and effort 2.

Frequently Asked Questions about technical-debt-prioritisation

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

FAQPage Schema
How do I prioritize technical debt items objectively instead of relying on gut feeling?

Prioritize technical debt using an evidence-based framework that scores items across impact, risk, and effort dimensions, categorizes debt by type, and identifies quick wins for systematic remediation.

What is the best way to build a technical debt remediation roadmap?

Build a remediation roadmap by scoring debt items on impact, risk, and effort, then generating multi-horizon plans spanning sprint, quarterly, and 6-month intervals to align with business priorities.

How does a three-dimensional scoring system work for technical debt categorization?

Three-dimensional scoring evaluates technical debt by assigning values to impact, risk, and effort, categorizing items into types like Code Quality or Architecture to identify quick wins and plan remediation.

Can I align technical debt remediation with business priorities using risk management?

Align technical debt remediation with business priorities by scoring risk and impact dimensions, categorizing the debt, and generating multi-horizon roadmaps that strategically sequence remediation work.

When should I use a structured framework for technical debt prioritization?

Use a structured framework for technical debt prioritization when facing a backlog of items and needing to objectively score each item, identify quick wins, and plan a remediation roadmap.

Does technical debt prioritization require dependency on the bc component?

Technical debt prioritization depends on the bc component to execute its advanced scripts and references, enabling systematic scoring and roadmap generation within the software engineering workflow.