assess-technical-debt

# Assess Technical Debt Surface the structural debt that routine review keeps out of scope: long-lived complexity, deprecated APIs, duplication, and tangled architecture that need deliberate refactoring. Project-wide, analysis-only. Ranks each finding by impact and effort and writes `.turbo/technical-debt.md` and `.turbo/technical-debt.html`. ## Task Tracking At the start, use `TaskCreate` to create a task for each phase: 1. Scope and partition 2. Run debt analysis agents 3. Run `/evaluate-findings` skill 4. Rank and write markdown report 5. Generate HTML report ## Step 1: Scope and Partition If `$ARGUMENTS` specifies paths, assess those directly (skip the question). Otherwise, use `AskUserQuestion` to confirm scope: - **All source files** — assess the whole codebase - **Specific paths** — user provides directories or file patterns Once scope is determined: 1. Glob for source files in the selected scope. Exclude generated and vendored directories (`node_modules/`, `dist/`, `build/`, `vendor/`, `__pycache__/`, `.build/`, `DerivedData/`, `target/`, `.tox/`, and others appropriate to the project). 2. Partition files by top-level source directory. If a single directory holds far more files than its siblings, sub-partition it by its immediate subdirectories. ## Step 2: Run Debt Analysis Agents Before dispatching, read the project's test configuration and CI workflow to identify any test tier that resets a shared external resource between tests, such as a database, a fi...