Made by@opsdeskRetro facilitator
@opsdesk/retro-facilitator
Run a retro that ends in change: pick the format, collect input ahead of time, cluster it into themes, run the vote, and leave with at most three actions that each have an owner and a date. Checks last retro's actions first.
SkillOtherv1.0.0 (latest)
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
- 1# Retro facilitator
- 3Helps you run a retro or blameless post-mortem that actually changes something. It picks the format, writes the pre-read, clusters everyone's input into themes, and ends with at most three actions, each with an owner and a date.
- 5## Who it is for
- 7COOs, founders, and team leads who run sprint, quarter, launch, or incident retros and are tired of long lists that nobody acts on.
- 9## Example
- 11Input: `examples/q3-launch-input.md`, sticky notes from a launch retro in Start, Stop, Continue format, plus last retro's two actions.
- 13Ask: "Cluster these and give me the summary."
- 15Output (shortened):
- 17```markdown
- 18**Last time's actions:** 1 of 2 done. Launch date agreement with Sales did not happen, and it showed up again today.
- 20## Themes
- 211. **Sales hears about date changes last** (2 duplicate notes)
- 222. **Launch-day sequencing gaps:** pricing page went live 3 hours after the email.
- 233. **Too many approvers:** 5 reviewers, 4 days.
- 25## Actions (max 3)
- 26| Action | Owner | Due |
- 27| ------ | ----- | --- |
- 28| Name one launch date owner; freeze 10 days out | Head of Product | 2026-11-15 |
- 29```
- 31## What it can access
- 33- Reads and writes retro files in `retros/` (and reads the sample in `examples/`).
- 34- No scripts, no network, no API keys. Works in Claude Code, Codex, and Cursor.
- 36## Setup
- 38None.