Skip to content

rampstackco/claude-skills / skills/sprint-operations

sprint-operations

Verified

Run 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.

references/review-template.md

View on GitHub
# Sprint Review Template

Review shows what shipped against the sprint goal and captures feedback as tickets. It is a working session with stakeholders, not a slideshow.

Timebox: about 30 minutes per week of sprint length.

---

## Agenda

1. **Goal.** Read the sprint goal. State plainly: met, partly met, or not met.
2. **Demo.** Show working software for each committed item that is done. Use staging or production, not screenshots, where possible.
3. **Acceptance.** For each item, the product owner accepts or rejects against the acceptance criteria.
4. **Not done.** List carryover and the reason for each, in one line.
5. **Feedback.** Capture every piece of feedback as a draft ticket or a note on an existing one.
6. **Look ahead.** Show the likely goal for next sprint and the top of the ready backlog.

---

## Record

```
SPRINT: [number or name]
DATE: [YYYY-MM-DD]
ATTENDEES: [names and roles]

SPRINT GOAL: [text]
RESULT: [met / partly met / not met]

DEMOED AND ACCEPTED
| Ticket | Title | Accepted by | Notes |
|---|---|---|---|

DEMOED AND REJECTED
| Ticket | Title | Criterion not met | Next step |
|---|---|---|---|

NOT DONE (CARRYOVER)
| Ticket | Title | Reason |
|---|---|---|

FEEDBACK CAPTURED
| Feedback | From | Ticket created or updated |
|---|---|---|

NEXT SPRINT PREVIEW
- Likely goal: [one line]
```

---

## Agent-lane work in review

Demo agent-produced changes the same way as any other. Note in the record which items came from an agent lane so review rework is traceable. Do not single them out in the demo; the acceptance bar is the same.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall