Retro skill

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines.

by phuryn·MIT license·★ 26,557 Stars on the repo·GitHub ↗

Use now

phuryn/main1 file shown

SKILL.md2.7 KB

Browse every file on GitHub↗

SKILL.md

Show the full text77 lines

retro/SKILL.md77 lines · 2.7 KB

PreviewCode

Outline

RawView on GitHub

Sprint Retrospective Facilitator

Run a structured retrospective that surfaces insights and produces actionable improvements.

Context

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.

Instructions

Choose a retro format based on context (or let the user pick):

Format A — Start / Stop / Continue:
- Start: What should we begin doing?
- Stop: What should we stop doing?
- Continue: What's working well that we should keep?
Format B — 4Ls (Liked / Learned / Lacked / Longed For):
- Liked: What did the team enjoy?
- Learned: What new knowledge was gained?
- Lacked: What was missing?
- Longed For: What do we wish we had?
Format C — Sailboat:
- Wind (propels us): What's driving us forward?
- Anchor (holds us back): What's slowing us down?
- Rocks (risks): What dangers lie ahead?
- Island (goal): Where are we trying to get to?
If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages):
- Group similar items into themes
- Identify the most frequently mentioned topics
- Note sentiment patterns (frustration, energy, confusion)
Analyze the sprint performance:
- Sprint goal: achieved or not?
- Velocity vs. commitment (over-committed? under-committed?)
- Blockers encountered and how they were resolved
- Collaboration patterns (what worked, what didn't)
Generate prioritized action items:

Priority Action Item Owner Deadline Success Metric

1 [Specific, actionable improvement] [Name/Role] [Date] [How we'll know it worked]
- Limit to 2-3 action items (more won't get done)
- Each must be specific, assignable, and measurable
- Reference previous retro actions if available — were they completed?

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.

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