rampstackco/claude-skills / skills/sprint-operations
sprint-operations
VerifiedRun the measurement and ceremony layer of a delivery team: the metric set, estimation and capacity, the five sprint ceremonies, and the sprint report and quarterly rollup. Use this skill whenever the user is acting as PMO or scrum lead, planning a sprint, running standup, refinement, review, or retro, measuring velocity, cycle time, or throughput, checking capacity, or reporting on how a team is doing. Triggers on PMO, sprint planning, plan the sprint, standup, refinement, backlog grooming, sprint review, retro, velocity, capacity, cycle time, lead time, throughput, WIP, burndown, carryover, sprint report, story points to hours, how is the team doing, delivery metrics, agent lanes. Also triggers when the user asks how much work fits in a sprint or whether a team is on track, even if they never say sprint or PMO.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 358 B |
| SKILL.md | skill md | 11.9 KB |
| references/capacity-checklist.md | markdown | 2.7 KB |
| references/example-sprint-report.md | markdown | 4.3 KB |
| references/metrics-reference.md | markdown | 5.9 KB |
| references/planning-template.md | markdown | 1.9 KB |
| references/refinement-template.md | markdown | 2.0 KB |
| references/retro-template.md | markdown | 2.5 KB |
| references/review-template.md | markdown | 1.5 KB |
| references/sprint-report-template.md | markdown | 2.3 KB |
| references/standup-template.md | markdown | 1.7 KB |
references/sprint-report-template.md
View on GitHub# Sprint Report Template
One page. Every number comes from the tracker. Each metric shows the last three sprints so the reader sees a trend, not a snapshot.
This is raw material. For an executive readout, shape it with `stakeholder-communication`.
---
## Template
```
# Sprint [N] report: [team name]
Dates: [start] to [end]
Prepared by: [name]
Data source: [tracker, export date]
## Goal
[Sprint goal text]
Result: [met / partly met / not met]. [One sentence on why.]
## Headline
[Two or three sentences. The most important thing a reader should take away.]
## Metrics
| Metric | Sprint [N-2] | Sprint [N-1] | Sprint [N] | Note |
|---|---|---|---|---|
| Throughput (tickets) | | | | |
| Points completed | | | | |
| Cycle time p50 / p85 (days) | | | | |
| Lead time p50 / p85 (days) | | | | |
| Average WIP | | | | |
| Carryover percent | | | | |
| Planned share | | | | |
| Rework rate | | | | |
## Agent lanes (if any)
| Metric | Sprint [N-2] | Sprint [N-1] | Sprint [N] | Note |
|---|---|---|---|---|
| Dispatches issued | | | | |
| Draft-PR cycle time p50 (hours) | | | | |
| Review rework rate | | | | |
| Honest-stop rate | | | | |
| Cost per merged PR | | | | |
## Carryover
| Ticket | Title | Reason | Plan |
|---|---|---|---|
## Unplanned work
| Ticket | Title | Source | Size |
|---|---|---|---|
## Risks and asks
- [Risk or ask, with owner]
## Retro actions
| Action | Owner | Due |
|---|---|---|
## Data gaps
[Anything that could not be computed, and why. Or "none."]
```
---
## Quarterly rollup additions
The quarterly rollup uses the same metric table with one column per sprint in the quarter, plus:
- **Points-to-hours ratio**, if finance uses one: this team's ratio, the sprints it was computed from, and the change from last quarter.
- **Estimate accuracy table**: median and 85th percentile cycle time per estimate bucket.
- **Changes tried**: the retro actions that shipped this quarter and what the metrics did after.
- **Agent-lane summary**: dispatches, merged PRs, honest-stop rate, and total cost, against the prior quarter.
---
## Writing the headline
Lead with the goal result and the one trend that matters most.
- Weak: "Good sprint. Team worked hard."
- Strong: "Goal met. Carryover fell for the third sprint in a row (31 to 18 percent) after the WIP limit went in. Review wait is now the bottleneck for agent PRs."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |