Facilitate a structured delivery retrospective — going beyond the sprint level to examine the full release or programme delivery, identify systemic patterns, and generate lasting improvements.
npx claudepluginhub devmuslim/pdm-skills --plugin pdm-metrics-reportingThis skill uses the workspace's default tool permissions.
Facilitate a structured delivery retrospective — going beyond the sprint level to examine the full release or programme delivery, identify systemic patterns, and generate lasting improvements.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
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.
Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
Facilitate a structured delivery retrospective — going beyond the sprint level to examine the full release or programme delivery, identify systemic patterns, and generate lasting improvements.
A retro is only valuable if it produces specific, owned, time-bound actions. Without those, it's just venting.
Liked — What went well that we should keep doing? Learned — What did we discover that we didn't know before? Lacked — What was missing that hurt our delivery? Longed For — What do we wish we had?
5 min — Set the Stage
15 min — Individual Reflection Each person writes sticky notes (or Miro cards) for each of the 4Ls.
20 min — Group and Theme Facilitator groups similar items. Team votes on top themes (dot voting).
20 min — Discuss Top 3 Themes For each theme: What happened? Why? What would we do differently?
15 min — Action Planning For each improvement: WHO does WHAT by WHEN. Maximum 3 actions per retro — focus beats quantity.
5 min — Close Rate the retro: Was it useful? (1–5) What would make it better?
| # | Improvement | Owner | Due Date | Status |
|---|---|---|---|---|
| 1 | Add dependency review to sprint planning | PDM | Next sprint | ⬜ Open |
| 2 | Create shared test environment for all teams | DevOps | 2 weeks | ⬜ Open |
| 3 | Run Three Amigos for all stories > 5 SP | PDM | Immediate | ⬜ Open |
Review retro actions at the start of the next retro. If an action is not done: either do it or explicitly drop it.
/lessons-learned or /working-agreements