retrospective-guide

name	retrospective-guide
description	Sprint retrospective templates and facilitation guides. Supports Keep/Problem/Try, 4Ls, Sailboat, and other formats with action item tracking across retros.
metadata	{"version":"1.0.0","category":"operations","domain":"agile"}
triggers	["retrospective","retro","sprint review","회고"]

Retrospective Guide - Sprint Retrospective Templates

Overview

Structured retrospectives that drive real improvement. The goal isn't to vent — it's to commit to one actionable change each sprint.

---

1. When to Apply

Trigger	Behavior
End of sprint	Retro template generation
"retro", "회고"	Interactive format selection
Post-incident	Incident-specific retro template

---

2. Retro Formats

Keep / Problem / Try (기본)

# Sprint [N] Retrospective — YYYY-MM-DD

## Keep (계속할 것)
- [What worked well and should continue]

## Problem (문제점)
- [What didn't work or caused friction]

## Try (시도할 것)
- [Specific experiments for next sprint]

## Action Items
| Action | Owner | Due | From |
|--------|-------|-----|------|
| [Specific action] | @name | [date] | Problem #1 |

4Ls (Liked, Learned, Lacked, Longed For)

## Liked 👍
- [What the team enjoyed]

## Learned 📚
- [New knowledge or insights gained]

## Lacked 😕
- [What was missing or insufficient]

## Longed For 🌟
- [What the team wishes they had]

Sailboat ⛵

## Wind (추진력) — What pushed us forward?
- [Accelerators]

## Anchor (방해) — What held us back?
- [Blockers and friction]

## Rocks (위험) — What risks lie ahead?
- [Upcoming risks]

## Island (목표) — Where are we heading?
- [Sprint/quarter goal]

---

3. Facilitation Tips

1. Review previous action items first (5 min)
2. Silent brainstorming → write sticky notes individually (5 min)
3. Group and vote on topics (5 min)
4. Discuss top 3 voted items (15 min)
5. Commit to 1-3 action items with owners and dates (5 min)
6. Total: 30-45 minutes

---

4. Anti-Patterns

Anti-Pattern	Fix
No action items	Always end with specific, owned actions
Same problems every retro	Track action item completion rate
Blame-focused	Establish "no blame" ground rule
Skipping retros "too busy"	This is how you GET less busy

---

5. Tool Coordination

Tool	Purpose
Write	Generate retro documents
Read	Reference previous retro action items

---

6. Boundaries

Will:

• Generate retro templates in multiple formats
• Track action items across retros
• Provide facilitation guidance

Will Not:

• Facilitate the actual meeting
• Judge team performance
• Share retro content outside the team