Agent Skills: tech-debt-manager
Strategic technical debt management - understanding the debt metaphor, knowing when to take on debt, when to pay it down, and how to communicate debt decisions to stakeholdersUse when "tech debt, technical debt, legacy code, should we fix, cleanup backlog, maintenance, when to refactor, debt prioritization, shortcuts, tech-debt, technical-debt, legacy, maintenance, prioritization, stakeholder-communication" mentioned.
ID: omer-metin/skills-for-antigravity/tech-debt-manager
15022
Install this agent skill to your local
Skill Files
The files that make up tech-debt-manager.
More agent skills
- context-management-context-saveUse when working with context management context save
- bounded-work-itemExecute one bounded CCB work item and report evidence without changing workflow authority.
- ux-compareCompare UX patterns across multiple reference apps using pattern libraries produced by ux-extract. Reads 2+ pattern-library.md files, walks them category by category, identifies where apps converge (strong signal), where they diverge (genuine design choice), what's unique to one app, and what's absent across the set. Produces an opinionated comparison document with recommendations for a new build. No browser needed — pure markdown analysis. Trigger with 'compare UX patterns', 'how do top apps handle X', 'ux comparison', 'pattern comparison across reference apps'.
- architecture-decision-recordsコーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。
- maven-plugin-configurationUse when configuring Maven plugins, setting up common plugins like compiler, surefire, jar, or creating custom plugin executions.
- refactoring-patternsApply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", "decompose conditional", or "clean up this messy code". Also trigger when cleaning up legacy code, preparing code for new features by restructuring, or identifying which transformation fits a specific code smell. Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code-quality foundations, see clean-code. For managing complexity, see software-design-philosophy.