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/refinement-template.md
View on GitHub# Refinement Template
Refinement gets the next one to two sprints of tickets to ready. It is where questions get answered before the sprint, not during it.
Timebox: about 5 to 10 percent of the sprint's working time, split into one or two sessions. Use `ticket-authoring` for the ticket formats and the definition of ready.
---
## Before the session
- [ ] Product owner has ordered the top of the backlog
- [ ] Each candidate ticket has a first draft from its template
- [ ] Open questions are written on the tickets, not held in someone's head
- [ ] Anything needing design or research has a spike or a design ticket already
---
## Agenda
1. **Re-check the top.** Has anything changed priority since last time?
2. **Walk each candidate.** For each ticket, in order:
- Read the title and the acceptance criteria or repro steps aloud.
- Run the definition-of-ready section for its type.
- Answer what can be answered now. Assign an owner and a date to what cannot.
- Estimate. If estimates spread widely, discuss the biggest and smallest, then re-estimate once.
- Split anything larger than about a third of one person's sprint.
3. **Mark ready.** Only tickets that pass the checklist get the ready label.
4. **Look ahead.** Is there enough ready work for the next sprint's target plus 25 percent?
---
## Record
```
DATE: [YYYY-MM-DD]
ATTENDEES: [names]
READY THIS SESSION
| Ticket | Type | Estimate | Notes |
|---|---|---|---|
NOT READY
| Ticket | Missing | Owner | By |
|---|---|---|---|
SPLIT
- [Original ticket] into [new tickets]
SPIKES CREATED
- [Spike title, timebox]
READY BACKLOG DEPTH: [N points or tickets] vs next sprint target [N]
```
---
## Estimation notes
- Estimate relative to recently finished tickets, not in hours.
- Check estimate accuracy quarterly (see `metrics-reference.md`). If two sizes have the same cycle time, discuss what really drives effort.
- Agent-lane tickets get estimated too. Draft-PR cycle time by estimate bucket tells you which sizes agents handle well.
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: 471k | 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 |