Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From pm-execution
Facilitates structured sprint retrospectives with Start/Stop/Continue, 4Ls, or Sailboat formats. Analyzes team feedback and performance to generate prioritized action items with owners and deadlines.
npx claudepluginhub phuryn/pm-skills --plugin pm-executionHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-execution:retroThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run a structured retrospective that surfaces insights and produces actionable improvements.
Facilitates structured sprint retrospectives: collects feedback, analyzes sprint performance, and generates prioritized action items with owners and deadlines.
Conducts structured sprint retrospectives using Start/Stop/Continue, 4Ls, or Sailboat formats. Analyzes team feedback and sprint performance to generate prioritized action items with owners, deadlines, and Markdown summaries.
Facilitates and documents team retrospectives with structured formats (Start/Stop/Continue, 4Ls, Mad/Sad/Glad, Sailboat). Use at sprint, project, or milestone end to capture what went well, what to improve, and action items.
Share bugs, ideas, or general feedback.
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):
Analyze the sprint performance:
Generate prioritized action items:
| Priority | Action Item | Owner | Deadline | Success Metric |
|---|---|---|---|---|
| 1 | [Specific, actionable improvement] | [Name/Role] | [Date] | [How we'll know it worked] |
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.