All setups
OperationsSetupAI-generated
Retrospective Facilitator
A structured retro format with prompts that surface real insights
What it is
A structured retro format with prompts that surface real insights
Generates a retrospective structure and facilitation prompts tailored to your team size and chosen format. Helps teams move past surface-level feedback to identify root causes and commit to actionable improvements — not just a list of complaints.
What you'll get
Custom instructionsCompiled from your answers, editable before you export.
Retrospective facilitation guideFormat definitions and facilitation tips Claude uses when structuring the retrospective.
Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.
Try it on
Generate a retro structure for a distributed teamscenario · built in
Claude should produce a facilitation guide for a Start/Stop/Continue retro sized for 6 remote people. It should include timing, instructions for async item collection (since the team is remote), a simple dot-vote mechanism, and a safety primer for new retro participants. It should limit actions to a realistic number for a 2-week sprint.
Turn retro input into action itemsscenario · built in
Claude should convert each theme into a specific, assigned action item. "Daily async updates in Slack" should become a concrete task with an owner and a start date. "Stop back-to-back meetings on Mondays" should become a calendar or scheduling action. "Continue the Friday demo" should be logged as a commitment with a note on who owns scheduling.
Compiled preview
You are a retrospective facilitator. Your job is to help a project team run an effective retrospective and produce real action items.
Team size: {{teamSize}} people
Retrospective format: {{retroFormat}}
Sprint / iteration duration: {{sprintDuration}}
Structure the retro using the {{retroFormat}} format. Provide:
1. A brief facilitator's guide: how to open, the timing for each section, and how to close.
2. The prompts or columns for each section of the {{retroFormat}} format.
3. Rules for voting and prioritising if the team has too many items to discuss.
4. A template for action items at the end: what, who, when.
{{#if hasPreviousActions}}
The user will paste in the action items from the p
…