agentleFS
Sign inStart free
scotidevscotidev/GameDevStudio/.agents/skills/tech-debt/SKILL.md

tech-debt

Skill1 starsChanged 8 months agoMITView on GitHub

Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.

36 other projects use a version of this, 11 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use soak-test, team-live-ops and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 9 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 9 projects that use this

  • +5 more from lilangMax

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill is invoked:

    line 8
  2. Distinctive:

    Search the codebase for debt indicators:

    line 17
  3. Very specific:

    Update the debt register at docs/tech-debt-register.md

    line 32
  4. Distinctive:

    Read the debt register

    line 39
  5. Distinctive:

    Every debt entry must explain WHY it was accepted (deadline, prototype, missing info)

    line 68

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When this skill is invoked:

  1. Parse the subcommand from the argument:
    • scan — Scan the codebase for tech debt indicators
    • add — Add a new tech debt entry manually
    • prioritize — Re-prioritize the existing debt register
    • report — Generate a summary report of current debt status
  2. For scan:
    • Search the codebase for debt indicators:
      • TODO comments (count and categorize)
      • FIXME comments (these are bugs disguised as debt)
      • HACK comments (workarounds that need proper solutions)
      • @deprecated markers
      • Duplicated code blocks (similar patterns in multiple files)
      • Files over 500 lines (potential god objects)
      • Functions over 50 lines (potential complexity)
    • Categorize each finding:
      • Architecture Debt: Wrong abstractions, missing patterns, coupling issues
      • Code Quality Debt: Duplication, complexity, naming, missing types
      • Test Debt: Missing tests, flaky tests, untested edge cases
      • Documentation Debt: Missing docs, outdated docs, undocumented APIs
      • Dependency Debt: Outdated packages, deprecated APIs, version conflicts
      • Performance Debt: Known slow paths, unoptimized queries, memory issues
    • Update the debt register at docs/tech-debt-register.md
  3. For add:
    • Prompt for: description, category, affected files, estimated fix effort, impact if left unfixed
    • Append to the debt register
  4. For prioritize:
    • Read the debt register
    • Score each item by: (impact_if_unfixed * frequency_of_encounter) / fix_effort
    • Re-sort the register by priority score
    • Recommend which items to include in the next sprint
  5. For report:
    • Read the debt register
    • Generate summary statistics:
      • Total items by category
      • Total estimated fix effort
      • Items added vs resolved since last report
      • Trending direction (growing / stable / shrinking)
    • Flag any items that have been in the register for more than 3 sprints
    • Output the report

Debt Register Format

## Technical Debt Register
Last updated: [Date]
Total items: [N] | Estimated total effort: [T-shirt sizes summed]

| ID | Category | Description | Files | Effort | Impact | Priority | Added | Sprint |
|----|----------|-------------|-------|--------|--------|----------|-------|--------|
| TD-001 | [Cat] | [Description] | [files] | [S/M/L/XL] | [Low/Med/High/Critical] | [Score] | [Date] | [Sprint to fix or "Backlog"] |

Rules

  • Tech debt is not inherently bad — it is a tool. The register tracks conscious decisions.
  • Every debt entry must explain WHY it was accepted (deadline, prototype, missing info)
  • "Scan" should run at least once per sprint to catch new debt
  • Items older than 3 sprints without action should either be fixed or consciously accepted with a documented reason

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free