sprint-summary
The sprint-summary Claude Code skill generates a comprehensive sprint report from Claude Code Agent Monitor data by querying session, analytics, and cost endpoints for a specified time period. Use it to review development productivity, costs, and performance metrics across projects during a sprint, producing a professional report with velocity trends, technology breakdowns, efficiency analysis, and retrospective insights for team leads or managers.
git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor /tmp/sprint-summary && cp -r /tmp/sprint-summary/plugins/ccam-productivity/skills/sprint-summary ~/.claude/skills/sprint-summarySKILL.md
# Sprint Summary
Generate a sprint summary from Claude Code Agent Monitor data.
## Input
The user provides: **$ARGUMENTS**
This may be:
- A sprint duration: "last 2 weeks", "last 10 days"
- A date range: "2025-03-31 to 2025-04-13"
- "current sprint" (default: last 14 days)
## Procedure
1. **Fetch sprint data** from `http://localhost:4820`:
- `GET /api/sessions?limit=500` — all sessions in range (default sort: most recently updated first)
- `GET /api/analytics` — aggregated metrics
- `GET /api/pricing/cost` — total costs
- For high-value sessions: `GET /api/events?session_id={id}` — event details
2. **Compile sprint summary**:
### 🎯 Sprint Overview
- Sprint period: [start] to [end]
- Total sessions: N (completed: N, errored: N, abandoned: N)
- Total development hours with Claude Code: N
- Total cost: $X.XX
- Overall completion rate: N%
### 📦 Deliverables
Group sessions by working directory (project):
- **Project A** (`/path/to/project`)
- N sessions, N hours, key activities
- **Project B** (`/path/to/other`)
- N sessions, N hours, key activities
### 📊 Velocity Metrics
| Metric | Sprint | Previous Sprint | Trend |
|--------|--------|-----------------|-------|
| Sessions/day | N | N | ↑/↓ |
| Avg session duration | Nm | Nm | ↑/↓ |
| Cost/session | $N | $N | ↑/↓ |
| Tokens/session | N | N | ↑/↓ |
| Completion rate | N% | N% | ↑/↓ |
### 🛠 Technology Breakdown
- Models used with distribution percentages
- Top 15 tools by usage with category grouping
- Subagent utilization rate
### ⚡ Efficiency Analysis
- Token efficiency: cache hit rate, compaction frequency
- Cost per completed task
- Time-to-first-output (avg across sessions)
- Error recovery rate (sessions that recovered from errors)
### 🔄 Retrospective Data Points
- **What went well**: Highest-efficiency sessions, best completion rates
- **What could improve**: Most expensive sessions, highest error rates
- **Action items**: Data-driven suggestions for next sprint
## Output Format
Professional sprint report suitable for sharing with team leads or managers:
- Executive summary paragraph (5 sentences max)
- Structured data tables with trend indicators
- Grouped deliverables by project
- Numbered action items at the endOperate and maintain the local MCP server for this repository. Use for MCP tool updates, policy-guard changes, host configuration, and MCP runtime troubleshooting.
Run release-readiness checks for this repository. Use when validating docs, scripts, verification coverage, and operational safety before merge or release.
Understand this repository quickly before making changes. Use for architecture discovery, ownership mapping, command selection, and initial implementation planning.
Review backend route and hook logic for regressions, data integrity risks, and missing tests.
Review React UI changes for behavior regressions, state consistency, and UX breakage.
Review MCP server changes for tool safety, schema quality, and host integration correctness.
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.
Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or adjusting safety policy flags.