tech-debt

Technical debt remediation is prioritized by analyzing repository findings across architecture, testing, documentation, and infrastructure, scoring categories using a 0–10 rubric with impact and effort to calculate priorities and generate a remediation plan.

Generate a technical debt report by analyzing the repository to produce a TECH_DEBT.md file containing an executive summary, scorecard, prioritized P1–P4 actions, and success metrics tailored for sprint planning.

You can use existing CI configuration, configured linters, and test frameworks to score technical debt findings. The analysis optionally leverages these tools to enrich the evaluation and produce an actionable remediation plan.

Git availability is required to analyze repository technical debt. The analysis depends on git to evaluate architecture, testing, documentation, and infrastructure categories and generate the prioritized remediation roadmap.

Identify high-impact, low-effort fixes by applying a comprehensive 0–10 scoring rubric that evaluates impact and effort across technical debt categories, calculating priorities to surface actionable items for the upcoming cleanup sprint.

Technical debt analysis delegates to available specialized skills for code-quality, linting, security, dependency, and design checks to enrich findings and produce a comprehensive prioritized remediation plan.