// Use when the user wants to find, catalog, or address technical debt. Also use when starting a cleanup sprint, looking for code quality improvements, or asking "what needs cleaning up?"
| name | techdebt |
| description | Use when the user wants to find, catalog, or address technical debt. Also use when starting a cleanup sprint, looking for code quality improvements, or asking "what needs cleaning up?" |
Systematically find technical debt across code and GitHub, then propose actionable fixes.
# Issues labeled as tech debt, cleanup, refactor, or similar
gh issue list --label "tech-debt,cleanup,refactor,chore" --state open --json number,title,labels,milestone
# Also check for stale PRs
gh pr list --state open --json number,title,createdAt,labels
Search for TODO/FIXME/HACK in code:
grep -rn "TODO\|FIXME\|HACK\|XXX\|WORKAROUND" src/ test/ --include="*.fs" --include="*.fsproj"
Check for common patterns using project-appropriate tools:
IDisposable without use binding (Constitution VI violation)with _ -> in request paths (Constitution VII violation)git worktree list showing abandoned branches| Priority | Category | Example |
|---|---|---|
| P0 | Constitution violations | Missing use, silent swallowing, duplicated logic |
| P1 | Existing GitHub issues | Tagged tech-debt issues in current milestone |
| P2 | Code smells | TODOs, dead code, test gaps |
| P3 | Housekeeping | Stale branches, dependency drift, formatting |
Output a table sorted by priority:
## Tech Debt Report — [date]
### P0: Constitution Violations (fix immediately)
| # | File:Line | Issue | Constitution |
|---|-----------|-------|-------------|
| 1 | src/Foo.fs:42 | StreamReader not disposed | VI |
### P1: Open GitHub Issues
| # | Issue | Title | Milestone |
|---|-------|-------|-----------|
### P2: Code Smells
| # | File:Line | Issue |
|---|-----------|-------|
### P3: Housekeeping
| # | Item | Action |
|---|------|--------|
**Quick wins** (< 30 min each): [list items that are fast to fix]
**Needs planning** (> 30 min): [list items that need a spec or plan]
For approved items:
Project board: Newly filed P2 issues should land on the Frank Roadmap project (https://github.com/orgs/frank-fs/projects/1). If the "Auto-add to project" workflow is enabled in the project's Workflows tab, this happens automatically; otherwise add manually with gh project item-add 1 --owner frank-fs --url <issue-url>. Set Track to Other (or the matching track if the debt is scoped to one) and Status to Ready.
Break an issue into tasks so small and precise that each has exactly one correct implementation. Refuses to launch execution until the plan contains actual code shapes, verified file paths, and scope locks. Use before any implementation session.
Use when implementing a milestone with multiple issues. Thesis-first approach: write failing E2E tests before issues, expert-review acceptance criteria before implementation, use dedicated terminal sessions (not subagents), and verify E2E yourself before merging. Includes review cycle that creates follow-up issues when expert review surfaces new gaps.
Babysit open PRs — auto-rebase, fix CI, address review comments. Use with /loop 5m /babysit for hands-free PR management.
Run Holzmann "Power of Ten" discipline review on changed code. Checks nesting depth, loop bounds, function size, preconditions, mutable state, side effect surfacing, and indirection depth. Use after writing code, before committing, or as part of PR review. Outputs a weighted letter grade (A-F) with stoplight color.
Use when completing a feature, before creating a PR, or when the user asks "what do my experts think?" Dispatches the expert panel as parallel subagents for structured code review from multiple perspectives.
Commit staged changes, push branch, and create a PR with full pre-flight verification.