# Lessons Learned Summarizer

> lessons-learned-summarizer

- Skill: `45ck/lessons-learned-summarizer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 45ck/lessons-learned-summarizer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/45ck/lessons-learned-summarizer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: 45ck (https://skillmd.com/u/45ck)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/45ck/lessons-learned-summarizer

---

# lessons-learned-summarizer

## Purpose
Summarize lessons learned into reusable, evidence-backed improvement statements.

## Trigger this skill when
- A project, delivery effort, or formal planning activity needs clearer control artifacts.
- Scope, risk, cost, schedule, communication, or closure signals need structured review.
- You need planning outputs that can feed engineering, governance, or assessment work.

## Expected inputs
- project history
- incidents
- retrospectives
- closure notes

## Deliverables
- lesson statements
- evidence snippets
- recommendations
- reusability notes

## Operating procedure
1. Clarify the project context, objective, and control horizon.
2. Separate what is known from what is assumed, estimated, or missing.
3. Produce the skill-specific artifact or review output.
4. Surface risks, tradeoffs, ownership gaps, and ethics concerns explicitly.
5. Recommend the next best handoff instead of trying to solve the whole lifecycle at once.

## Quality gates
- The output is specific to the current project context.
- Uncertainty, assumptions, and decision dependencies are visible.
- The result is usable by a PM, engineering lead, or project team.
- Lessons should be framed as reusable guidance backed by concrete evidence.

## Handoff targets
- project-charter-writer
- risk-register-builder
- stakeholder-comms-planner

## Output style
- Be explicit about scope, timing, cost, risk, and governance tradeoffs.
- Prefer operational artifacts over broad managerial prose.
- Surface evidence gaps instead of inventing certainty.
- Keep the result usable in real project documents and repo workflows.

## Failure modes to avoid
- Do not confuse aspiration with approved commitment.
- Do not hide uncertainty inside a neat-looking plan.
- Do not treat every stakeholder or deliverable as equally critical.
- Do not sever planning artifacts from execution reality.

## Minimum output skeleton
```md
## Summary
## Findings
## Structured outputs
## Risks / blockers
## Open questions
## Recommended next skill
```