matthew-a-carr/review-tech-debt
Review and triage the tech debt register. Use when the user says "review tech debt," before planning a new feature, or on a periodic schedule. Reads docs/tech-debt.md, assesses each item's relevance and severity, categorises actions, and reports recommendations to the human.
81
94%
Does it follow best practices?
Impact
76%
1.24xAverage score across 1 eval scenario
Passed
No known issues
task.mdevals/scenario-1/
Tech Debt Triage Report
Problem Description
A backend engineering team has accumulated a set of unresolved tech debt items over the past year. Before kicking off a new quarter of feature work, the engineering manager has asked for a thorough triage of all outstanding items so the team knows what to prioritise, what can be knocked out quickly, what needs its own planning, and what can safely wait.
The tech debt register lives at docs/tech-debt.md. Each entry references a spec in docs/specs/ that describes the original feature and the deviation that created the debt. The manager needs a clear written report so they can decide with the team which items to act on in the next sprint.
Output Specification
Produce a file called tech-debt-report.md containing your triage findings. The report must cover all outstanding items in the register, assess each one, and organise recommendations into clearly labelled sections. For each item include your reasoning.
Do not modify any of the input files — the report is the only output expected.