tech-debt

MDT Technical Debt Detection Workflow (v2)

On-demand detection of technical debt patterns in implemented code.

Core Principle: Identify structural problems introduced during implementation. Every debt item must have concrete file locations, evidence, and fix direction.

User Input

$ARGUMENTS

Session Context

Use {TICKETS_PATH} in all file path templates below (if it's not defined read ticketsPath key from .mdt-config.toml).

Output Location

{TICKETS_PATH}/{CR-KEY}/debt.md

Execution Steps

Step 1: Extract Project Context

Detect or extract from CLAUDE.md / project config:

project:
  source_dir: {src/, lib/, app/, ...}
  test_command: {npm test, pytest, cargo test, go test, make test, ...}
  build_command: {npm run build, cargo build, go build, make, ...}
  file_extension: {.ts, .py, .rs, .go, .java, ...}

If CLAUDE.md exists, read it. Otherwise detect from project files.

Step 2: Load CR Context

1. Call MCP tool mdt-all:get_cr with mode="full" — abort if CR doesn't exist
2. Extract:
   • Affected/new artifacts — files to analyze
   • Architecture Design — check for violations
   • Acceptance Criteria — extract scope/boundary constraints to verify
3. Load requirements if exists: Check {TICKETS_PATH}/{CR-KEY}/requirements.md
   • If found: check for unsatisfied requirements (debt indicator)
4. Load tasks if exists: Check {TICKETS_PATH}/{CR-KEY}/tasks.md
   • If found: check Requirement Coverage table for gaps
5. If codebase available, scan actual files

Step 3: Detect Debt Patterns

Analyze against these patterns:

Pattern	Signal	Severity
Duplication	Same logic in 2+ locations	High
Shotgun Surgery	Adding X requires editing N files	High
Missing Abstraction	Concept in code without type/interface	Medium
Hidden Coupling	Module imports internals of another	Medium
Responsibility Diffusion	Single concern across 3+ files	High
Unsatisfied Requirements	Requirements with no implementing code	High