Skill

Skill: lessons-learned

Document and share lessons learned after a release — so the team and organization benefit from experience, and the same mistakes aren't repeated.

Install

npx claudepluginhub devmuslim/pdm-skills --plugin pdm-metrics-reporting

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Document and share lessons learned after a release — so the team and organization benefit from experience, and the same mistakes aren't repeated.

SKILL.md

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

139.0k

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

bmad-distillator

7 files

Compresses source documents into lossless, LLM-optimized distillates preserving all facts and relationships. Use for 'distill documents' or 'create distillate' requests.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Skill: lessons-learned

Purpose

Document and share lessons learned after a release — so the team and organization benefit from experience, and the same mistakes aren't repeated.

When to Use

Within 2 weeks after every major release
After a failed or significantly delayed delivery
As input to the next release planning cycle

Framework: Lessons Learned Document

Step 1 — Gather Input

Collect from: retrospective outputs, post-mortem reports, PDM notes, team feedback.

Step 2 — Lessons Learned Document

Release / Programme: [Name] Period: [Start date] – [End date] Prepared By: [PDM Name] Date: [Date]

What Went Well ✅ Document practices to repeat:

[Example: Early dependency mapping prevented 3 integration issues]
[Example: Three Amigos sessions reduced bug count by 30%]

What Didn't Go Well ❌ Document issues without blame:

[Example: App Store review timeline underestimated — caused 2-week delay]
[Example: UAT environment was not stable — slowed business testing]

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

[Specific change to planning process]
[Specific change to quality process]
[Specific change to stakeholder management]

Output Format

Full lessons learned document (ready for Confluence)
Action items for next release planning
Suggested next command: /plan-release or /risk-register