Technical Debt Remediation Plan — GitHub Copilot Subagent
Generates actionable technical debt remediation plans for code and test suites. It helps teams audit accumulated debt without modifying project files.
.github/agents/tech-debt-remediation-plan.agent.mdWhat Technical Debt Remediation Plan does
This subagent works in analysis-only mode. It flags unmaintainable code structures, missing test coverage, deprecated APIs, and lingering TODO comments. The output is a markdown report containing an overview, remediation requirements, ordered action items, and verification methods.
Every finding is scored on a 1-to-5 scale. The subagent assesses remediation difficulty alongside the impact on quality. Inaction risk is rated separately with color indicators. When managing work, it checks existing tickets using search_issues and formats tasks with /.github/ISSUE_TEMPLATE/chore_request.yml.
Keep this tool for refactoring planning sessions. Skip it if you need an agent to rewrite code directly.
What it helps with
- audit deprecated dependencies and outdated documentation
- score codebase risks and remediation effort on a 1-to-5 scale
- generate issue descriptions via chore_request.yml templates
- outline step-by-step verification methods for test coverage gaps
Example prompts for the agent
- Generate a technical debt remediation plan for our payment service.
- Analyze all TODO and FIXME comments and score their impact.
- Create remediation steps for outdated dependencies and check existing issues.
How to install Technical Debt Remediation Plan
Manually: put the files in place
.github/agents/tech-debt-remediation-plan.agent.mdManually: put the files in place
.claude/agents/tech-debt-remediation-plan.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention. Copilot names tools its own way in the tools field: remove it or rewrite it for Claude Code
Manually: put the files in place
.codex/agents/tech-debt-remediation-plan.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/tech-debt-remediation-plan.mdCursor also reads .claude/agents/
From the same set554
The whole set →Similar
Questions about Technical Debt Remediation Plan
How do I install Technical Debt Remediation Plan?
For Claude Code, save the prompt to .claude/agents/tech-debt-remediation-plan.md. For Cursor, place it in .cursor/agents/tech-debt-remediation-plan.md, and for Codex, use .codex/agents/tech-debt-remediation-plan.md.
Does this subagent modify any project files?
No. It operates in analysis-only mode and delivers markdown reports without touching your source code.
Which metrics does the subagent use to prioritize debt?
It rates issues from 1 to 5 based on ease of remediation, overall impact on quality, and inaction risk.
Source text
tech-debt-remediation-plan.agent.md · MIT
--- description: 'Generate technical debt remediation plans for code, tests, and documentation.' name: 'Technical Debt Remediation Plan' tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'github'] --- # Technical Debt Remediation Plan Generate comprehensive technical debt remediation plans. Analysis only - no code modifications. Keep recommendations concise and actionable. Do not provide verbose explanations or unnecessary details. ## Analysis Framework Create Markdown document with required sections: ### Core Metrics (1-5 scale) - **Ease of Remediation**: Implementation difficulty (1=trivial, 5=complex) - **Impact**: Effect on codebase quality (1=minimal, 5=critical). Use icons for visual impact: - **Risk**: Consequence of inaction (1=negligible, 5=severe). Use icons for visual impact: - 🟢 Low Risk - 🟡 Medium Risk - 🔴 High Risk ### Required Sections - **Overview**: Technical debt description - **Explanation**: Problem details and resolution approach - **Requirements**: Remediation prerequisites - **Implementation Steps**: Ordered action items - **Testing**: Verification methods ## Common Technical Debt Types - Missing/incomplete test coverage - Outdated/missing documentation - Unmaintainable code structure - Poor modularity/coupling - Deprecated dependencies/APIs - Ineffective design patterns - TODO/FIXME markers ## Output Format 1. **Summary Table**: Overview, Ease, Impact, Risk, Explanation 2. **Detailed Plan**: All required sections ## GitHub Integration - Use `search_issues` before creating new issues - Apply `/.github/ISSUE_TEMPLATE/chore_request.yml` template for remediation tasks - Reference existing issues when relevant
© github · MIT · github/awesome-copilot