tech-debt

<!-- Generated from `.claude/skills/_available/engineering/tech-debt/SKILL.md` by `scripts/generate-agents-skills.py`. Do not edit. --> # Technical debt review ## When to use Use this skill when a component, project, or portfolio needs a defensible technical- debt inventory, duplicate cleanup, cost-of-delay comparison, or security-risk review. Do not use it to modify code, close tickets, set a sprint commitment, or certify a security issue as safe. Not for calling ordinary feature requests or unsupported complaints technical debt without linked evidence. ## Inputs and source discipline Set the review scope and as-of date/time. Search code, configuration, tests, build logs, incident reviews, operational measurements, issue discussions, and dated notes. For every candidate capture a source, source date, as-of date/time, stable locator (path/line, commit, ticket, or record), and any freshness or access limitation. Linked code and operational evidence should identify the underlying problem, not just repeat a label such as "refactor later". Keep first-seen provenance separate from current discovery. A dated source can support `first-seen`; an undated mention cannot establish age. Record `first-seen: unknown` when no dated evidence exists rather than guessing an age or inventing an aging bucket. ## Method 1. Gather candidates read-only and normalize each into one underlying debt item: affected component, debt mechanism, observable consequence, evidence links, and cur...