- name
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating a
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add phuryn/pm-skills --skill retro -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add phuryn/pm-skills --skill retro -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add phuryn/pm-skills --skill retro -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add phuryn/pm-skills --skill retro -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/phuryn/pm-skills/tree/HEAD/pm-execution/skills/retroFrom the publisher
Run a structured retrospective that surfaces insights and produces actionable improvements.
You are facilitating a retrospective for $ARGUMENTS.
If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.
Choose a retro format based on context (or let the user pick):
Format A — Start / Stop / Continue:
Format B — 4Ls (Liked / Learned / Lacked / Longed For):
Format C — Sailboat:
If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages):
If there is no input yet, collect it anonymously before the discussion, so the first or most senior voice doesn't set the agenda: a word cloud or a 1–5 rating for the mood, and written items others can upvote for what went well and what didn't. The live-polls and live-qa skills cover both.
Analyze the sprint performance:
Generate prioritized action items:
Create the retro summary:
## Sprint [X] Retrospective — [Date]
### Sprint Performance
- Goal: [Achieved / Partially / Missed]
- Committed: [X pts] | Completed: [Y pts]
### Key Themes
1. [Theme] — [summary]
### Action Items
1. [Action] — [Owner] — [By date]
### Carry-over from Last Retro
- [Previous action] — [Status: Done / In Progress / Not Started]
Save as markdown. Keep the tone constructive — the goal is improvement, not blame.
© 2026 Skills Rack.
---name: retrodescription: Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with…---# pm-execution/skills/retro/SKILL.mdOverview
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
FAQ
Download pm-execution/skills/retro/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/phuryn/pm-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.