Files
settled-reach/whatsinagame/templates/.claude/skills/health-check/SKILL.md
T
jpmschweitzerandClaude Opus 4.6 b025fe8152 chore(db): remove db/connectors backwards-compat symlink (#568)
Remove the db/connectors → tooling/db/ symlink added in Sprint 21
(#274) and migrate all references to use tooling/db/ directly.

- Delete tracked symlink from db/connectors
- Remove duplicate db/connectors/* permission patterns from settings
- Update project-structure.md to reflect removal
- Move whatsinagame/static/db/connectors/ to whatsinagame/static/tooling/db/
- Update 20 whatsinagame template, skill, and test files
- Update comment references in client/tests/test_anti_tedium.gd
- Historical docs (old sprint briefings, changelog, discussions) left as-is

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-28 22:13:26 +01:00

2.0 KiB

name, description, user-invocable, allowed-tools
name description user-invocable allowed-tools
health-check Generate team health metrics dashboard. Use when the user says "health check", "metrics", "team health", or invokes /health-check. Calculates sprint velocity, cycle time, PR turnaround, and decision coverage. true Bash, Read, Grep, Glob

Team Health Check

Generate a team health metrics dashboard covering sprint velocity, cycle time, PR turnaround, and decision coverage.

Workflow

1. Sprint Metrics

Calculate velocity and throughput trends:

tooling/db/sqlite-query "SELECT s.name, COUNT(CASE WHEN t.status='done' THEN 1 END) as done, COUNT(t.id) as total FROM sprints s LEFT JOIN tickets t ON t.sprint_id = s.id GROUP BY s.id ORDER BY s.id DESC LIMIT 5"

Compute:

  • Velocity: tickets completed per sprint (trend over last 3 sprints)
  • Cycle time: average time from in_progress to done
  • Completion rate: done / (done + carry-over)

2. Code Review Metrics

From git and PR history:

  • Total PR count and merge rate for the period
  • Time to first review (from PR open to first comment/approval)
  • Approval vs. rejection rate

3. Decision Coverage

Check alignment between decisions and implementation:

  • Active decisions without implementing tickets (orphans)
  • Decisions per domain file (architecture, perception, content, scope)
  • Open questions (Q-NNN items) and their age

4. Backlog Health

Assess the overall backlog state:

  • Total backlog size grouped by priority
  • Tickets without a team assignment
  • Stale tickets: no update in 30+ days

5. Output

Format as a structured dashboard:

## Team Health — {date}

### Sprint Velocity (last 3)
| Sprint | Done | Total | Rate |
|--------|------|-------|------|

### Cycle Time
Average: N days | Trend: improving/stable/declining

### Decision Coverage
| Domain | Decisions | With Tickets | Gap |
|--------|-----------|-------------|-----|

### Backlog
Total: N | Unassigned: N | Stale (30d+): N

### Risks
- {risk items with context and suggested actions}