Skip to content
Back to skills

Ls Technical Debt Planning

ASecurity

Guide technical-debt audits and backlog shaping. Use to identify, rank,

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsgitapisecurity

Works with

  • api

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add CruxExperts/LocalSetup --skill ls-technical-debt-planning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ls Technical Debt Planning?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ls Technical Debt Planning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cruxexperts-ls-technical-debt-planning/badge)](https://www.skillsdirectory.com/skills/cruxexperts-ls-technical-debt-planning)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ls-technical-debt-planning
description: Guide technical-debt audits and backlog shaping. Use to identify, rank,
  scope, and plan debt work without opportunistic rewrites.
metadata:
  version: '1.0'
extensions:
  external_skill:
    source_kind: native-reference
    source_url: https://github.com/anthropics/knowledge-work-plugins
    source_path: engineering/skills/tech-debt/SKILL.md
    source_commit: a84404cb0156a15702c9ecf4d16051346cacce49
    source_ref: main
    source_sha256: ed3b4b1450c0fd9b8dad17313b5a4fafd8e6947d380b79b36a2e8259f3b1df0f
    license: Apache-2.0
    import_date: '2026-07-03'
    vetting_status: provenance-recorded-no-bundled-tooling-executed
---

# 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`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.