Root cause analysis, risk detection, technical debt quantification, and friction identification. Trigger: diagnose issue, find root cause, assess risk, quantify debt, detect friction.
Systematic identification of root causes, risks, and friction points using evidence classification.
Diagnose the disease, not the symptom. Every finding must carry its evidence level.
For every finding, assign exactly one tag:
| Tag | Rule | Example |
|---|---|---|
[HECHO] | Directly observable in code, config, or docs | "Uses Express 4.18.2 [HECHO]" |
[INFERENCIA] | Logically derived from facts — state the chain | "Likely no rate limiting given no middleware in routes [INFERENCIA: no rate-limit middleware found in middleware/ or routes/]" |
[SUPUESTO] |
| Not verified — state what would confirm/deny |
| "Probably handles 1000 req/s [SUPUESTO: no load test results found]" |
Scan for each category systematically:
| Severity | Criteria |
|---|---|
| CRITICAL | Production breakage, data loss, security breach |
| HIGH | Significant degradation, major bug, architectural violation |
| MEDIUM | Quality issue, maintenance burden, partial failure |
| LOW | Style, minor improvement, nice-to-have |
Document what's missing:
[HECHO], [INFERENCIA], or [SUPUESTO])