lessons-learned

Create a lessons-learned register DOCX from retrospective notes.

Updated Apr 19, 2026

Search Tags:#documentation #retrospective #project-management #knowledge-base #lessons-learned

Ready to run

npx skills add https://github.com/kenmulford/PMSkills --skill lessons-learned-kenmulford

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lessons-learned
Source: https://github.com/kenmulford/PMSkills/tree/main/skills/lessons-learned
Command: npx skills add https://github.com/kenmulford/PMSkills --skill lessons-learned-kenmulford

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-docx, and includes scripts (resource) components.

What problem does it solve?

Captures and standardizes project reflections into a structured lessons-learned register, preserving user phrasing and preventing fabrication of root causes or balanced positives.

Core Features & Use Cases

Enforces honesty with never-invent root causes and preserves exact user wording.
Generates a DOCX with sections for Keep Doing, Change Next Time, and Appendix to support project closeouts and retrospectives.
Supports phase-gate retrospectives, post-mortems, and retrospective writeups requiring a concise, auditable history of what happened, why, and what to change.

Quick Start

Describe a project retrospective in plain language and run the skill to produce a Lessons Learned document.

Frequently Asked Questions about lessons-learned

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a lessons-learned document from a project post-mortem without fabricating root causes?▼

This Skill automates the creation of a lessons-learned register from retrospective notes by preserving exact user phrasing and rendering a structured DOCX document with Keep Doing, Change Next Time, and Appendix sections.

What is the best way to document phase-gate retrospective notes into an auditable history?▼

Yes, the Skill enforces Project+ guardrails that prevent inventing root causes and preserve exact user phrasing, allowing you to automate project closeout writeups from retrospective notes accurately.

Do I need python-docx installed to generate a lessons-learned register?▼

The Skill renders a DOCX document with Keep Doing, Change Next Time, and Appendix sections, providing an auditable history of what happened, why, and what to change for phase-gate retrospectives.

How do I prevent fabricated root causes when capturing project lessons from a retrospective?▼

Yes, python-docx is a required dependency because the Skill uses it to render the structured lessons-learned register into a DOCX document format.

What is the best way to standardize project reflections into a structured lessons-learned register?▼

The Skill enforces Project+ guardrails that never invent root causes and preserve exact user phrasing, ensuring impacts and recommendations are captured verbatim from retrospective notes without fabrication.

How do I capture honest project lessons for future success from retrospective notes?▼

Describe a project retrospective in plain language and run the Skill to produce a standardized lessons-learned register that preserves user phrasing and prevents fabrication of balanced positives.