Skill

retrospective-guide

Sprint retrospective templates and facilitation guides. Supports Keep/Problem/Try, 4Ls, Sailboat, and other formats with action item tracking across retros.

From forged-claude-code

Install

Run in your terminal

npx claudepluginhub dokkabei97/forged-claude-code --plugin forged-claude-code

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Stars1

Forks0

Last CommitMar 1, 2026

Actions

View Source View Plugin View on GitHub View README

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

Review previous action items first (5 min)
Silent brainstorming → write sticky notes individually (5 min)
Group and vote on topics (5 min)
Discuss top 3 voted items (15 min)
Commit to 1-3 action items with owners and dates (5 min)
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