Retrospective Facilitation

This helps you run better team retrospectives by giving you structured formats, facilitation techniques, and templates for end-of-sprint or post-incident reviews. You get planning checklists, action item tracking patterns, and multiple retrospective formats like "Went Well / Didn't Go Well / Ideas" to keep things from getting stale. The guides emphasize psychological safety and converting feedback into actual action items with owners, which is where most retros fall apart. Good if you're facilitating these ceremonies and want to avoid the common traps like blame games, no follow-through, or the same three people dominating every discussion. Works for remote teams with virtual collaboration tools or in-person sessions.

skills.sh installs: 451
GitHub stars: 379
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aj-geddes/useful-ai-prompts --skill retrospective-facilitation --agent claude-code

Installs into .claude/skills of the current project.

Files

Overview

Retrospectives are critical ceremonies for team learning and continuous improvement. Effective facilitation creates psychological safety, encourages honest feedback, and drives tangible improvements.

When to Use

End of sprint (regular cadence)
Major milestone completion
Project closure
After significant events or incidents
Team transitions or staff changes
Technology implementations
Process evaluations

Quick Start

Minimal working example:

Retrospective Planning:

Event: Sprint 23 Retrospective
Date: Friday, Jan 17, 2025
Duration: 60 minutes
Location: Conference Room B / Zoom

Facilitator: Sarah (Scrum Master)
Participants: 8 team members
Invite: Product Owner (optional)

---
Retrospective Goals: 1. Celebrate sprint successes
  2. Identify what went well
  3. Identify what could improve
  4. Commit to specific improvements
  5. Build team cohesion

SKILL.md on GitHub