ls-tech-debt

Guide technical-debt audits and backlog shaping. Use to identify, rank, scope, and plan debt work without opportunistic rewrites.

SKILL.md

GitHub

Technical Debt

Use this skill when working on technical debt tasks.

Workflow

  • Tie each debt item to an observable cost: incidents, slow delivery, flaky tests, security risk, support load, or onboarding drag.
  • Separate cleanup, risk reduction, migration, and feature work; avoid mixing them in one diff.
  • Define smallest useful debt payment with validation and rollback criteria.

Boundaries

  • Inspect the target repository before making changes.
  • Prefer existing project patterns, declared package managers, and documented validation commands.
  • Do not expose secrets, credentials, private user data, or production account identifiers in source, examples, or logs.
  • When external APIs or current vendor behavior matter, verify against official docs before implementation.

Provenance

  • Source: https://github.com/anthropics/knowledge-work-plugins
  • Ref: main at a84404cb0156a15702c9ecf4d16051346cacce49
  • Source path: engineering/skills/tech-debt/SKILL.md
  • License classification: Apache-2.0
  • Source SHA-256: ed3b4b1450c0fd9b8dad17313b5a4fafd8e6947d380b79b36a2e8259f3b1df0f