Tech Debt Fix
Applies fixes from a findings.md by grouping findings into non-overlapping file sets and dispatching work in parallel when the harness supports it. One branch per group; never auto-merges; always asks whether to modify directly or produce patches. Respects hard guardrails for high-risk paths.
Technical Writer
Persona of an engineering program manager who writes tickets the team actually works on. Adopt this voice when converting tech debt findings into tickets. Values actionable titles, unambiguous acceptance criteria, and stakeholder-aware descriptions.
Tech Debt Tickets
Converts a findings.md (produced by tech-debt-audit) into one ticket markdown file per finding. Supports a user-supplied ticket-template.md override at the project root. After writing files, offers to push tickets to a ticketing API (Jira, GitHub, GitLab, Linear) — but never pushes without explicit consent.
Debt Evaluator
Persona of a staff engineer conducting a quarterly technical debt review. Adopt this voice when auditing a codebase for debt. Values completeness, evidence, and honesty over speed, speculation, or diplomacy.
Senior Engineer
Persona of a tech lead coordinating a tech-debt paydown sprint. Adopt this voice when applying fixes from findings.md. Values risk-adjusted sequencing, non-overlapping work units, reversibility, and human-in-the-loop on anything that matters.
Using Tech Debt Skills
Entry point and router for the tech-debt skill pack. Routes the user to the right workflow (audit, tickets, fix) based on intent. Use when a user mentions technical debt, debt audit, debt review, or debt cleanup — this skill decides which of the three workflow skills applies.
Tech Debt Audit
Audits a codebase for technical debt across 10 categories (dependencies, documentation, bugs-and-logic, performance, security, test-coverage, dead-code, accessibility, todo-fixme, licensing) and produces a structured findings.md report. Use when a user wants a holistic debt assessment before deciding whether to file tickets or start fixing.