Stats
Actions
Tags
From ai-pm-assistant
Facilitates sprint or project retrospectives and synthesizes raw team notes into structured, action-oriented retro documents. Works in two modes: planning a retro session or post-sprint synthesis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-pm-assistant:retrospective <sprint name + retro notes, or "plan a retro"><sprint name + retro notes, or "plan a retro">This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
$ARGUMENTS
$ARGUMENTS
If no input is provided above, ask: "Are you planning a retro or writing one up? For a write-up, paste the team's notes (what went well, what didn't, ideas). For planning, tell me the sprint and team size."
Two modes - infer from the input, or ask:
| Mode | When | Output |
|---|---|---|
| Facilitate | Before the session - need a format and prompts | Retro plan + prompts |
| Synthesise | After - have raw notes | Structured retro with owned actions |
If raw notes are present, go straight to Synthesise.
| Input | Required? | Notes |
|---|---|---|
| Sprint / period | Yes | Anchors the retro |
| Raw notes or themes | Yes (Synthesise) | What the team said |
| Sprint metrics | No | Velocity, carryover, incidents - adds evidence |
| Prior retro actions | No | Were last retro's actions done? |
Duration: [e.g. 60 min] | Team: [N] | Format: [Start/Stop/Continue, 4Ls, Sailboat]
Goal: Surface what to change next sprint - not to assign blame.
Agenda
| Time | Block | Purpose |
|---|---|---|
| 0-5 | Set the stage | Restate sprint goal + outcome |
| 5-10 | Review last retro's actions | Did we do them? |
| 10-30 | Gather (silent then share) | What went well / what didn't |
| 30-45 | Group + vote | Cluster themes, dot-vote top 3 |
| 45-58 | Actions | One owned action per top theme |
| 58-60 | Close | Confirm owners and check-in date |
Prompts
Date: [Today] | Attendees: [Roles] | Sprint outcome: [Met / Partially met / Missed goal]
| Last Retro Action | Owner | Done? |
|---|---|---|
| [Action] | [Who] | Yes / No / Partial |
(Omit if first retro.)
| # | Theme | What happened | Impact |
|---|---|---|---|
| 1 | [Theme] | [Specific, blameless] | [Cost to team/delivery] |
| # | Action | Owner | By When | Addresses |
|---|---|---|---|---|
| 1 | [Concrete, testable change] | [Person] | [Date] | [Theme #] |
Each action has one owner and a date. "Communicate better" is not an action - "Post the deploy plan in #releases by Wed standup" is.
If the input doesn't give an owner or date for an action, do not fabricate one. Assign the most likely owner from context and mark it [confirm at retro], or use [Owner TBC] / [Date TBC], and flag that each must be set before the retro closes.
[One line: team morale and any signal worth watching.]
Follow the Saving Artefacts rules in .claude/claude.md. Default local path: clients/CLIENT/sprint-artefacts/YYYY-MM-DD-sprint-N-retro.md. Then suggest carrying the action items into the next /sprint-planning.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub erica-j-01/ai-pm