Stats
Actions
Tags
Document and share lessons learned after a release — so the team and organization benefit from experience, and the same mistakes aren't repeated.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pdm-metrics-reporting:lessons-learnedThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Document and share lessons learned after a release — so the team and organization benefit from experience, and the same mistakes aren't repeated.
Document and share lessons learned after a release — so the team and organization benefit from experience, and the same mistakes aren't repeated.
Collect from: retrospective outputs, post-mortem reports, PDM notes, team feedback.
Release / Programme: [Name] Period: [Start date] – [End date] Prepared By: [PDM Name] Date: [Date]
What Went Well ✅ Document practices to repeat:
What Didn't Go Well ❌ Document issues without blame:
Lessons Learned
| # | Lesson | Category | Recommendation | Owner | Apply From |
|---|---|---|---|---|---|
| L1 | App Store review takes 10–14 days, not 5 | Planning | Add 2-week buffer for all mobile releases | PDM | Next release |
| L2 | UAT env needs dedicated infra — shared env caused conflicts | Quality | Provision dedicated UAT environment | DevOps | Q3 |
| L3 | Weekly stakeholder pulse caught concerns early | Comms | Continue monthly pulse surveys | PDM | Ongoing |
Metrics Comparison
| Metric | Planned | Actual | Variance |
|---|---|---|---|
| Release date | Jun 30 | Jul 14 | +14 days |
| Scope delivered | 100% | 87% | -13% |
| P0 bugs post-launch | 0 | 2 | +2 |
| Team NPS | — | 7.2/10 | — |
Recommendations for Next Release
/plan-release or /risk-registernpx claudepluginhub devmuslim/pdm-skills --plugin pdm-metrics-reportingRuns a post-release retrospective: collects session logs, test results, and scope data; analyzes delivery, quality, and process; extracts lessons; generates a retro document and optional increment request for the next iteration.
Produces structured retrospectives after major releases or deprecations, comparing plan vs actual outcomes on blast radius, communication, migration, and support to identify process improvements.
Activate for: retrospective, retro, post-mortem, post launch review, feature review, what went well, what didn't go well, lessons learned, sprint retrospective, product review, launch review, did it work, measure impact, feature retrospective, post-ship review, outcome review, product retro, evaluate feature success. NOT for: metrics dashboards (use official /metrics-review), stakeholder updates (use official /stakeholder-update), sprint planning (use official /sprint-planning).