Retrospective
Open-source Claude skills for Program Management in product development — charters, status reports, RAID logs, roadmaps, launch readiness, retros, postmortems, OKRs & more.
npx -y skills add janellecipriano/pm-skills --skill retrospectiveAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Facilitate and write up a team retrospective — what went well, what didn't, and owned, time-bound action items. Use when the user says "run a retro", "retrospective", "sprint retro", "project post-completion review", "lessons learned", or wants to turn raw retro notes into a structured summary with follow-ups.
SKILL.md
1.8 KB, as published. Nobody here has run it
Retrospective
Help a team reflect productively and leave with a small number of concrete, owned improvements — not a venting session.
When to use
- End of a sprint, milestone, project, or quarter.
- Turning messy retro notes/transcript into a clean writeup.
- Designing a retro format/agenda.
Note: for incidents/outages use postmortem (blameless, root-cause focused) instead.
Inputs to gather
- What's being retro'd and the timeframe; who participated.
- Raw input if any (notes, sticky-note dump, transcript), or run a structured prompt.
Process
- Pick a frame — What went well / What didn't / What to try, or Start–Stop–Continue, or Mad–Sad–Glad.
- Group raw input into themes; don't list every duplicate sticky.
- Keep it blameless — focus on systems and process, not individuals.
- Surface the 2–4 highest-leverage improvements, not a wishlist. Each becomes an action.
- For every action: owner, concrete next step, due date, and where it's tracked.
- Revisit prior retro actions — were they done? Open loops kill trust in retros.
Output format
## Retro — {{team/project}} · {{period}}
### What went well
- {{theme}}
### What didn't / challenges
- {{theme}}
### Action items
| Action | Owner | Due | Status |
| --- | --- | --- | --- |
### Carryover from last retro
- {{item — done? / still open}}
Keep actions few and real. A retro with 12 actions has zero.