Claude-Code-Game-Studios/.claude/skills/tech-debt/SKILL.md at ad540fe75dbfaf7af8764cf4b7d969f08c602395

mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-06-27 04:51:46 +00:00

Files

Donchitos ad540fe75d Game Studio Agent Architecture — complete setup (Phases 1-7)

48 coordinated Claude Code subagents for indie game development:
- 3 leadership agents (creative-director, technical-director, producer)
- 10 department leads (game-designer, lead-programmer, art-director, etc.)
- 23 specialist agents (gameplay, engine, AI, networking, UI, tools, etc.)
- 12 engine-specific agents (Godot, Unity, Unreal with sub-specialists)

Infrastructure:
- 34 skills (slash commands) for workflows, reviews, and team orchestration
- 8 hooks for commit validation, asset checks, session management
- 11 path-scoped rules enforcing domain-specific standards
- 28 templates for design docs, reports, and collaborative protocols

Key features:
- User-driven collaboration protocol (Question → Options → Decision → Draft → Approval)
- Engine version awareness with knowledge-gap detection (Godot 4.6 pinned)
- Phase gate system for development milestone validation
- CLAUDE.md kept under 80 lines with extracted doc imports

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-13 21:04:24 +11:00

3.1 KiB

Raw Blame History

name, description, argument-hint, user-invocable, allowed-tools

name	description	argument-hint	user-invocable	allowed-tools
tech-debt	Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.	[scan\|add\|prioritize\|report]	true	Read, Glob, Grep, Write

When this skill is invoked:

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
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
For add:
- Prompt for: description, category, affected files, estimated fix effort, impact if left unfixed
- Append to the debt register
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
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

3.1 KiB Raw Blame History

Debt Register Format

Rules

3.1 KiB

Raw Blame History