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/standup-template.md
View on GitHub# Daily Standup Template
Standup exists to surface blockers and WIP problems while they are still cheap. It is not a status report to a manager. If the team leaves without a blocker owned, the meeting did nothing.
Timebox: 15 minutes. Run it from the board, not from people.
---
## Format: walk the board
Go right to left: the column closest to done first. Ask about tickets, not about people.
1. **Closest to done.** What does it take to finish this today?
2. **In review.** Who is reviewing, and when? Agent PRs waiting on review go here.
3. **In progress.** Anything stuck for more than a day?
4. **WIP check.** Is anyone holding more than the WIP limit? Is anything started that should be paused?
5. **Blockers.** Name each one, give it an owner, and take the discussion offline.
6. **Goal check.** Are we still on track for the sprint goal? Yes, at risk, or no.
---
## Record (only what changed)
```
DATE: [YYYY-MM-DD]
BLOCKERS
| Ticket | Blocker | Owner | Needed by |
|---|---|---|---|
| | | | |
WIP OVER LIMIT
- [Person or lane]: [N] in progress, limit [N]. Action: [what pauses]
SPRINT GOAL: [on track / at risk / off track]
If at risk: [one line why]
FOLLOW-UPS AFTER STANDUP
- [Topic] with [names]
```
---
## Agent lanes at standup
The person who issued the dispatch reports for the lane:
- Which dispatches are running, which returned a result, which returned a blocker
- Which agent PRs are waiting on review, and how long they have waited
- Any honest stop that needs a human decision today
An agent PR waiting two days for review is a blocker. Treat it like one.
---
## Anti-patterns
- Round-robin "yesterday, today, blockers" with no board on screen
- Problem-solving in the meeting instead of after it
- Reporting hours worked
- Skipping the goal check
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 |