retro

Name: retro
Author: phuryn

1.7kinstalls2.5kforks

How to install retro?

phuryn/pm-skills/retro

$npx -y skills add phuryn/pm-skills --skill retro

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	## Sprint Retrospective Facilitator
2
3	Run a structured retrospective that surfaces insights and produces actionable improvements.
4
5	### Context
6
7	You are facilitating a retrospective for $ARGUMENTS.
8
9	If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.
10
11	### Instructions
12
13	1. Choose a retro format based on context (or let the user pick):
14
15	Format A — Start / Stop / Continue:
16	- Start: What should we begin doing?
17	- Stop: What should we stop doing?
18	- Continue: What's working well that we should keep?
19
20	Format B — 4Ls (Liked / Learned / Lacked / Longed For):
21	- Liked: What did the team enjoy?
22	- Learned: What new knowledge was gained?
23	- Lacked: What was missing?
24	- Longed For: What do we wish we had?
25
26	Format C — Sailboat:
27	- Wind (propels us): What's driving us forward?
28	- Anchor (holds us back): What's slowing us down?
29	- Rocks (risks): What dangers lie ahead?
30	- Island (goal): Where are we trying to get to?
31
32	2. If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages):
33	- Group similar items into themes
34	- Identify the most frequently mentioned topics
35	- Note sentiment patterns (frustration, energy, confusion)
36
37	3. Analyze the sprint performance:
38	- Sprint goal: achieved or not?
39	- Velocity vs. commitment (over-committed? under-committed?)
40	- Blockers encountered and how they were resolved
41	- Collaboration patterns (what worked, what didn't)
42
43	4. Generate prioritized action items:
44
45	\| Priority \| Action Item \| Owner \| Deadline \| Success Metric \|
46	\|---\|---\|---\|---\|---\|
47	\| 1 \| [Specific, actionable improvement] \| [Name/Role] \| [Date] \| [How we'll know it worked] \|
48
49	- Limit to 2-3 action items (more won't get done)
50	- Each must be specific, assignable, and measurable
51	- Reference previous retro actions if available — were they completed?
52
53	5. Create the retro summary:
54	```
55	## Sprint [X] Retrospective — [Date]
56
57	### Sprint Performance
58	- Goal: [Achieved / Partially / Missed]
59	- Committed: [X pts] \| Completed: [Y pts]
60
61	### Key Themes
62	1. [Theme] — [summary]
63
64	### Action Items
65	1. [Action] — [Owner] — [By date]
66
67	### Carry-over from Last Retro
68	- [Previous action] — [Status: Done / In Progress / Not Started]
69	```
70
71	Save as markdown. Keep the tone constructive — the goal is improvement, not blame.

People who liked this also viewed

6 picks

Type

retro

1.7kinstalls2.5kforks

View on GitHub

How to install retro?

phuryn/pm-skills/retro

$npx -y skills add phuryn/pm-skills --skill retro

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Sprint Retrospective Facilitator
2
3	Run a structured retrospective that surfaces insights and produces actionable improvements.
4
5	### Context
6
7	You are facilitating a retrospective for $ARGUMENTS.
8
9	If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.
10
11	### Instructions
12
13	1. Choose a retro format based on context (or let the user pick):
14
15	Format A — Start / Stop / Continue:
16	- Start: What should we begin doing?
17	- Stop: What should we stop doing?
18	- Continue: What's working well that we should keep?
19
20	Format B — 4Ls (Liked / Learned / Lacked / Longed For):
21	- Liked: What did the team enjoy?
22	- Learned: What new knowledge was gained?
23	- Lacked: What was missing?
24	- Longed For: What do we wish we had?
25
26	Format C — Sailboat:
27	- Wind (propels us): What's driving us forward?
28	- Anchor (holds us back): What's slowing us down?
29	- Rocks (risks): What dangers lie ahead?
30	- Island (goal): Where are we trying to get to?
31
32	2. If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages):
33	- Group similar items into themes
34	- Identify the most frequently mentioned topics
35	- Note sentiment patterns (frustration, energy, confusion)
36
37	3. Analyze the sprint performance:
38	- Sprint goal: achieved or not?
39	- Velocity vs. commitment (over-committed? under-committed?)
40	- Blockers encountered and how they were resolved
41	- Collaboration patterns (what worked, what didn't)
42
43	4. Generate prioritized action items:
44
45	\| Priority \| Action Item \| Owner \| Deadline \| Success Metric \|
46	\|---\|---\|---\|---\|---\|
47	\| 1 \| [Specific, actionable improvement] \| [Name/Role] \| [Date] \| [How we'll know it worked] \|
48
49	- Limit to 2-3 action items (more won't get done)
50	- Each must be specific, assignable, and measurable
51	- Reference previous retro actions if available — were they completed?
52
53	5. Create the retro summary:
54	```
55	## Sprint [X] Retrospective — [Date]
56
57	### Sprint Performance
58	- Goal: [Achieved / Partially / Missed]
59	- Committed: [X pts] \| Completed: [Y pts]
60
61	### Key Themes
62	1. [Theme] — [summary]
63
64	### Action Items
65	1. [Action] — [Owner] — [By date]
66
67	### Carry-over from Last Retro
68	- [Previous action] — [Status: Done / In Progress / Not Started]
69	```
70
71	Save as markdown. Keep the tone constructive — the goal is improvement, not blame.

People who liked this also viewed

6 picks

Type