tech-debt

## Phase 1: Parse Subcommand Determine the mode from the argument: - `scan` — Scan the codebase for tech debt indicators - `add` — Add a new tech debt entry manually - `prioritize` — Re-prioritize the existing debt register - `report` — Generate a summary report of current debt status If no subcommand is provided, output usage and stop. Verdict: **FAIL** — missing required subcommand. --- ## Phase 2A: Scan Mode Search the codebase for debt indicators: - `TODO` comments (count and categorize) - `FIXME` comments (these are bugs disguised as debt) - `HACK` comments (workarounds that need proper solutions) - `@deprecated` markers - Duplicated code blocks (similar patterns in multiple files) - Files over 500 lines (potential god objects) - Functions over 50 lines (potential complexity) Categorize each finding: - **Architecture Debt**: Wrong abstractions, missing patterns, coupling issues - **Code Quality Debt**: Duplication, complexity, naming, missing types - **Test Debt**: Missing tests, flaky tests, untested edge cases - **Documentation Debt**: Missing docs, outdated docs, undocumented APIs - **Dependency Debt**: Outdated packages, deprecated APIs, version conflicts - **Performance Debt**: Known slow paths, unoptimized queries, memory issues Present the findings to the user. Ask: "May I write these findings to `docs/tech-debt-register.md`?" If yes, update the register (append new entries, do not overwrite existing ones). Verdict: **COMPLETE** — scan findings written...