/sprint-status - Sprint Status Report

Get a quick status update on the current sprint.

Usage

/sprint-status [--detailed]

Arguments:

• --detailed - Include per-story breakdown

Examples

/sprint-status
/sprint-status --detailed

What It Shows

Summary View (Default)

• Sprint name and dates
• Days remaining
• Progress metrics (story points, tickets)
• Burndown status
• Blockers and risks

Detailed View

• All stories with status
• Assignment breakdown
• Velocity comparison
• Carry-over risk

Output Format

## Sprint Status: Sprint 23

**Dates:** Jan 8 - Jan 19, 2024
**Days Remaining:** 5

### Progress
| Metric | Done | In Progress | To Do |
|--------|------|-------------|-------|
| Stories | 8 | 4 | 3 |
| Points | 21 | 13 | 8 |
| Bugs | 5 | 2 | 0 |

### Burndown

Points 42 |**** 35 | **** 28 | **** 21 | **** <- Ideal 21 | ***** <- Actual (on track) +------------------- Day 1 5 10

### Blockers (2)
1. **PROJECT-789** - Waiting on API spec from external team
2. **PROJECT-812** - CI pipeline failing intermittently

### At Risk
- **PROJECT-801** - Complex story, may need carry-over

### Team Velocity
- Sprint 22: 38 pts
- Sprint 21: 42 pts
- Average: 40 pts
- Current pace: 39 pts (on track)

Skill Used

jira-reporting

When to Use Agent Instead

Use the Project Manager agent when:

• Detailed timeline analysis needed
• Stakeholder report required
• Risk mitigation planning