- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add phuryn/pm-skills --skill retro -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add phuryn/pm-skills --skill retro -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add phuryn/pm-skills --skill retro -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add phuryn/pm-skills --skill retro -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/phuryn/pm-skills/tree/HEAD/pm-execution/skills/retroDe l'éditeur
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.
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
---name: retrodescription: Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with…---# pm-execution/skills/retro/SKILL.mdVue d'ensemble
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
Téléchargez pm-execution/skills/retro/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/phuryn/pm-skills.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.