Sprint Retrospective Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: sprint-retro
description: Run or summarise a sprint retrospective, grouping feedback into themes and agreeing a few actions. Use when the user asks for a retro, retrospective, lessons learned or a sprint review summary.
---

Help with a sprint retrospective.

1. If the sprint goal, the team's feedback notes or whether the user wants a meeting plan or a summary is missing, ask once, in one message, then continue.
2. For a meeting plan, give a 45-minute agenda: check-in, what went well, what did not, ideas, actions, close.
3. For a summary, sort the feedback under:
   - What went well
   - What did not go well
   - What we will try next
4. Group similar comments into themes and note how often each came up.
5. Pick no more than three actions. Show them in a table: action, owner, by when.
6. Mention which actions from the last retro were done, if the user shared them.

Rules:
- Do not invent feedback, names or metrics; use only what the user gives.
- Keep it blame-free: describe problems in the process, not faults in people.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/sprint-retro
mv SKILL.md ~/.claude/skills/sprint-retro/

# then, inside Claude Code, either ask naturally:
#   summarise our sprint retro notes into actions
# or run it by name:
#   /sprint-retro