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/planning-template.md
View on GitHub# Sprint Planning Template
Planning produces three things: a sprint goal, a committed list of ready tickets, and the capacity math that justifies the size of that list.
Timebox: about one hour per week of sprint length. Come in with the capacity checklist already run.
---
## Agenda
1. **Last sprint in two minutes.** Goal met or not. Carryover and why.
2. **Capacity.** Read out the planning target from the capacity checklist.
3. **Goal.** Propose one sprint goal. Agree on it before choosing tickets.
4. **Select.** Pull ready tickets that serve the goal, in priority order, up to the target.
5. **Check.** Confirm every ticket is ready and nothing is larger than a third of one person's sprint.
6. **Commit.** Snapshot the committed list in the tracker.
---
## Planning record
```
SPRINT: [number or name]
DATES: [start] to [end]
FACILITATOR: [name]
LAST SPRINT
- Goal met: [yes / partly / no]
- Carryover: [N tickets, N points]. Reasons: [one line each]
CAPACITY
- Person-days available: [N] of [N] (ratio [0.xx])
- Trailing median: [N points or tickets] over sprints [list]
- Unplanned buffer: [N], from trailing planned share [0.xx]
- Carryover rolling forward: [N]
- Planning target for new work: [N]
AGENT LANES (if any)
- Dispatches planned: [N]
- Reviewer capacity reserved: [N person-days]
SPRINT GOAL
[One sentence. What will be true at the end of the sprint that is not true now.]
COMMITTED
| Ticket | Title | Estimate | Owner or lane |
|---|---|---|---|
| | | | |
Total: [N]
STRETCH (not committed)
| Ticket | Title | Estimate |
|---|---|---|
RISKS
- [Risk and who is watching it]
COMMITTED LIST SNAPSHOT TAKEN: [yes, timestamp]
```
---
## Writing a sprint goal
A goal is an outcome, not a list.
- Weak: "Finish tickets 412, 415, 419, and 420."
- Strong: "Managers can schedule and see overnight shifts in staging."
If the committed tickets do not add up to the goal, change one or the other before committing.
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 |