Log and prioritize technical debt items with impact and effort details.
npx skills add https://github.com/devmuslim/pdm-skills --skill tech-debt-log
Please help me install this Agent Skill. Skill: tech-debt-log Source: https://github.com/devmuslim/pdm-skills/tree/main/pdm-cross-team-coordination/skills/tech-debt-log Command: npx skills add https://github.com/devmuslim/pdm-skills --skill tech-debt-log
This Skill addresses the challenge of hidden technical debt that slows down delivery velocity and introduces risk by providing a structured way to log, prioritize, and negotiate time for its resolution.
Use the tech-debt-log skill to create a new entry for 'Auth service has no unit tests' in the 'Auth' area, noting it has a 'High' impact on delivery and requires '5 days' effort.
High-intent search queries and answers about installing and using this skill.
You can track technical debt by maintaining a structured log that records item descriptions, impacted areas, delivery impact, required effort, priority, date, and owner. This makes hidden delivery risks visible and facilitates stakeholder negotiation for resolution time.
Prioritize technical debt by classifying items based on their impact on delivery velocity and potential for failure or security issues. This risk-based classification helps engineering leads determine which code quality issues require immediate sprint capacity.
Negotiate time for technical debt reduction by applying a structured framework like the 20% rule, which allocates a fixed percentage of sprint capacity to address prioritized debt items, ensuring system maintainability without halting feature delivery.
Yes, a technical debt log is designed to capture recurring code quality issues identified in retrospectives. Logging these items with their delivery impact provides a clear business case for allocating dedicated development time.
A technical debt item is defined by its negative impact on delivery velocity, potential to introduce system failure or security issues, required remediation effort, affected code area, assigned owner, and the date it was logged.
freedomw1987Track, prioritize, and plan technical debt with standardized entry formats.
pacphiStandardize software quality consultancy practices for client engagements.
coolbeevipAnalyze technical debt via read-only inspection and evidence-based reports.
HeadyAIAnalyze codebases and designs for structure, patterns, and risks.
