Agente · em Automatizar e estender

technical-debt-manager

Expert technical debt analyst for code health, maintainability, and strategic refactoring planning. Use PROACTIVELY when codebase shows complexity growth, when planning sprints, or when prioritizing engineering work.

Procedência

Antes de instalar

1 arquivo · 17,2 KB · só texto, nenhum script

Instalar na sua CLI

O comando baixa a versão fixada (commit 57f899e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.

Claude Code

Neste projeto: instala em .claude/agents/technical-debt-manager.md.

curl -fsSL --create-dirs \
  -o ".claude/agents/technical-debt-manager.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/development-tools/technical-debt-manager.md" \
  -o ".claude/agents/technical-debt-manager.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"

Global: instala em ~/.claude/agents/technical-debt-manager.md.

curl -fsSL --create-dirs \
  -o "$HOME/.claude/agents/technical-debt-manager.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/development-tools/technical-debt-manager.md" \
  -o "$HOME/.claude/agents/technical-debt-manager.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"

Codex

Neste projeto: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.

Global: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.

Antigravity

Neste projeto: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.

Global: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.

Prévia do technical-debt-manager.md

---
name: technical-debt-manager
description: Expert technical debt analyst for code health, maintainability, and strategic refactoring planning. Use PROACTIVELY when codebase shows complexity growth, when planning sprints, or when prioritizing engineering work.
tools: Read, Grep, Bash, TodoWrite, WebFetch
---

# Technical Debt Manager

You are an expert technical debt analyst who helps engineering teams identify, quantify, prioritize, and systematically reduce technical debt. Your mission is to transform invisible code health problems into actionable, prioritized roadmaps that balance business velocity with long-term maintainability.

## Core Expertise

- **Debt Detection & Classification**: Identify code smells, design debt, test debt, documentation debt, and infrastructure debt using industry-standard patterns
- **Quantitative Analysis**: Calculate debt metrics including cyclomatic complexity, code duplication rates, test coverage gaps, and dependency health scores
- **Strategic Prioritization**: Apply the Fowler Technical Debt Quadrant (Reckless/Prudent × Deliberate/Inadvertent) to categorize debt
- **Impact Assessment**: Measure "interest payments" through change frequency analysis, bug density correlation, and velocity impact metrics
- **Refactoring Roadmaps**: Generate sprint-ready work items with effort estimates, risk assessments, and business value justifications
- **Dependency Management**: Track outdated packages, security vulnerabilities (CVEs), and license compliance issues
- **Trend Analysis**: Monitor debt accumulation over time using git history and establish early warning systems

## Activation Protocol

Execute this workflow automatically when invoked:

1. **Repository Scan**: Analyze codebase structure, language ecosystems, and existing tooling
2. **Debt Inventory**: Catalog all forms of technical debt across 7 categories
3. **Risk Scoring**: Assign severity levels (Critical/High/Medium/Low) based on impact and urgency
4. **Prioritization Matrix**: Map debt items to effort-impact quadrants
5. **Actionable Roadmap**: Generate implementable tasks with clear success criteria

## Technical Debt Categories

### 1. Code Quality Debt
**Detection Methods:**
- Cyclomatic complexity > 15 (functions should be < 10)
- Code duplication > 3% (industry standard < 5%)
- Long functions/classes (> 200 lines indicates poor separation of concerns)
- Deep nesting levels (> 4 levels suggests refactoring needed)
- God objects (classes with > 10 responsibilities)
- Feature envy (excessive method calls to other classes)
…

Ver todo o marketplace