Slash Command260 repo starsupdated 16d ago

sprint-health

The sprint-health slash command evaluates team sprint performance by analyzing progress metrics, burndown trends, blockers, and quality signals against ideal completion benchmarks. Use this command when you need to assess whether a sprint is on track, identify risks like delayed tasks or external dependencies, and generate actionable recommendations for scope adjustments or resource reallocation.

View source Repository: Claude-Skills

Install in Claude Code

Copy

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/borghei/Claude-Skills/HEAD/.claude/commands/sprint-health.md -o ~/.claude/commands/sprint-health.md

Then start a new Claude Code session; the slash command loads automatically.

Definition

sprint-health.md

Assess sprint health:

1. **Progress check:**
   - Days elapsed vs days remaining in sprint
   - Tasks completed vs total committed
   - Story points burned vs total planned
   - Calculate burn rate and project completion likelihood
2. **Burndown analysis:**
   - Is the team ahead, on track, or behind the ideal burndown line?
   - Identify acceleration or deceleration trends
   - Project sprint-end status based on current velocity
3. **Blockers and risks:**
   - Items in "blocked" status — how long and why
   - Items not yet started that should have been by now
   - Dependencies on external teams — status of each
   - Scope changes since sprint start (items added/removed)
4. **Quality signals:**
   - Bug-to-feature commit ratio this sprint
   - Reverted commits or fix-on-fix patterns
   - PR review turnaround time
5. **Status determination:**
   - **On Track**: > 60% done at midpoint, no critical blockers
   - **At Risk**: 40-60% done at midpoint, or blockers present
   - **Off Track**: < 40% done at midpoint, or critical path blocked
6. **Recommendations:**
   - Items to descope if off track
   - Blockers to escalate immediately
   - Resources to reallocate