菜单
Tech debt inventory, paydown strategy, prioritization (Critical/High/Medium/Low), deprecation planning, communicating to stakeholders, refactoring initiatives. Use when managing technical debt, planning paydown, or assessing refactoring ROI.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
SDK development, external developer communication, code samples, API client libraries, community engagement, and developer experience. Use when creating SDKs, writing external guides, creating code samples, or improving developer experience.
Profile systems, identify bottlenecks, optimize code and infrastructure for speed, throughput, and resource efficiency.
This skill should be used when implementing code quality standards, setting up linting/testing/security scans, enforcing coverage thresholds, or establishing CI/CD guardrails.
WCAG 2.1 AA compliance, keyboard navigation, screen reader testing, semantic HTML, ARIA labels, color contrast, assistive technology validation. Use when ensuring accessibility, conducting a11y audits, testing with screen readers, or designing inclusive interfaces.
REST/gRPC API design, versioning strategies, error codes, request/response contracts, backward compatibility, rate limiting, OpenAPI specifications. Use when designing APIs, defining contracts, planning versioning, or ensuring API consistency.
Hermetic builds, dependency management, build caching, reproducible builds, cross-compilation, build optimization. Use when optimizing build speed, ensuring reproducibility, or designing build infrastructure.
| name | skill-tech-debt |
| description | Tech debt inventory, paydown strategy, prioritization (Critical/High/Medium/Low), deprecation planning, communicating to stakeholders, refactoring initiatives. Use when managing technical debt, planning paydown, or assessing refactoring ROI. |
| version | 1.0.0 |
Track, prioritize, and pay down tech debt systematically. Don't let it spiral.
Impact × Effort Matrix:
LOW EFFORT → HIGH EFFORT
HIGH | Quick wins | Strategic |
IMPACT | | |
LOW | Skip (low ROI)| Avoid |
Quick wins: High impact, low effort → Do first
Strategic: High impact, high effort → Plan next quarter
Skip: Low impact, any effort → Only if free time
## Tech Debt Inventory: [Service]
### CRITICAL (Ship next sprint)
- [ ] Remove Python 2 support (ends 2025, blockers future deps)
- Effort: 2 weeks
- Impact: Unblocks 5 dependencies
- Owner: Backend lead
### HIGH (Backlog, 10% capacity/sprint)
- [ ] Refactor auth middleware (5 places copy-pasted)
- Effort: 1 week
- Impact: Reduces bugs, improves maintainability
- Owner: TBD
### MEDIUM (Nice to have)
- [ ] Extract common utils from 3 services
- Effort: 3 weeks (spans services)
- Impact: Code reuse
### LOW (Skip unless free time)
- [ ] Rename internal variable
- Effort: 1 hour
- Impact: Readability (minimal)
Allocate 10% of sprint to tech debt:
Communicate ROI:
Tech debt paydown: Remove Python 2 support
- Effort: 2 weeks (1 engineer)
- Unblocks: 5 dependencies (new features)
- Prevents: 3+ security issues (old Python 2 libs)
- ROI: High (enables future work)
v1.0: Old API endpoint alive
v1.5: Announce deprecation (email, docs)
v2.0: Mark endpoints as "deprecated" (header warning)
v2.5: Remove endpoint (6 months later)
Status: Ready for tech debt management
Best for: Debt prioritization, paydown planning, refactoring