Rule Title Here
Impact: LEVEL (impactDescription)
1-2 sentences explaining why this rule matters for managing technical debt.
How to Detect
# Tooling command or grep patternIncorrect
// ❌ Bad pattern — what debt looks likeProblems:
- Problem 1
- Problem 2
Correct
// ✅ Remediated patternBenefits:
- Benefit 1
- Benefit 2
Remediation Strategy
- Effort: S | M | L
- When to pay down: (e.g., before adding next feature, during dedicated sprint, on first touch)
Reference: Link