Tech Debt

Turn a vague sense of "this codebase needs work" into a ranked register: each item quantified by interest (how often and how badly it slows work) over principal (effort to pay it down). High-interest, low-principal debt is paid first — the same logic as finishing over starting. Read-only on code; files issues only on request.

Contract

Inputs:

• A repo or directory to assess; optional issues to file the register.

Outputs:

• A debt register: each item with type, evidence (file:line or metric), interest, principal, and a priority score.
• On request, one GitHub issue per selected item.