mcpField
R
retrospective-facilitation

retrospective-facilitation

github.com/aj-geddesProductivity373447 installsUpdated 34w ago
Repository

About retrospective-facilitation

A facilitation skill for planning and running team retrospectives. It offers reference guides on techniques, templates, and action tracking, with guidance for turning feedback into improvements.

Key features

  1. 01Retrospective planning guidance
  2. 02Facilitation technique references
  3. 03Action item tracking guidance
  4. 04Reusable retrospective templates
  5. 05Psychological safety practices

Use cases

  1. 01Running end-of-sprint reviews
  2. 02Reviewing a project milestone or closure
  3. 03Reflecting after incidents or team changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill retrospective-facilitation

After installing, type/retrospective-facilitationin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
action-item-tracking.md
facilitation-techniques.md
retrospective-planning.md
retrospective-templates.md
templates/
process-template.md

Details

From the project README

Retrospective Facilitation

Table of Contents

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

Format: "Went Well / Didn't Go Well / Ideas"
Tool: Miro board for virtual collaboration

Pre-Retrospective Preparation:
  - Send survey: anonymous feedback (24hrs before)
  - Gather sprint metrics (velocity, bugs, etc.)
  - Review sprint goals and outcomes
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Retrospective PlanningRetrospective Planning
Facilitation TechniquesFacilitation Techniques
Action Item TrackingAction Item Tracking
Retrospective TemplatesRetrospective Templates

Best Practices

✅ DO
  • Hold retrospectives regularly (every sprint)
  • Create psychological safety upfront
  • Use varied formats to maintain engagement
  • Include the whole team
  • Focus on systems, not individuals
  • Convert insights to specific action items
  • Assign clear owners and due dates
  • Track and celebrate completed actions
  • Review previous actions at start
  • Thank people for participation and honesty
❌ DON'T
  • Blame individuals or teams
  • Let dominant voices control discussion
  • Create action items without owners
  • Have retrospectives without follow-up
  • Ignore difficult feedback
  • Focus only on what went wrong
  • Hold retrospectives when people are tired/stressed
  • Skip closing/celebration
  • Mix retrospectives with status meetings
  • Ignore patterns across multiple retrospectives

Comments

Markdown supported