lessons-learned

Generates a lessons learned document capturing project successes, challenges, and recommendations.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill lessons-learned-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lessons-learned
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/closure/lessons-learned
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill lessons-learned-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project teams often finish work without systematically capturing what went well, what failed, and what to change, so the same mistakes repeat across projects. This Skill produces a structured, sign-off-ready lessons learned document during Phase 13 (Closure) of the SDLC. ## Core Features & Use Cases - Structured Retrospective Documentation: Generates a complete lessons learned document covering successes, challenges, root cause analysis, metrics, and recommendations. - Governed Sign-Off Workflow: Enforces validation rules, prerequisite signature checks, and Project Manager approval before the document is accepted. - Traceable Sources File: Writes a sources file recording predecessor documents, question history, and information gaps for auditability. - Use Case: After a project closes, a project manager invokes the skill to compile team feedback, defect logs, and closure report data into a signed lessons learned document stored at documentation/13-closure/lessons-learned.md. ## Quick Start Ask the agent to generate the lessons learned document for your completed project using the signed closure report and team retrospective input.

Frequently Asked Questions about lessons-learned

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

FAQPage Schema
How do I create a lessons learned document for a completed project?▼

Invoke the lessons-learned skill after the closure report is signed. Provide the project name, duration, team size, key successes, challenges, and recommendations, and the skill generates a structured Markdown document at documentation/13-closure/lessons-learned.md.

What inputs are required to generate lessons learned documentation?▼

The skill requires the signed closure report, the risk log from the roadmap, and team retrospective feedback. A defect log from the defect-log skill is recommended but optional.

Can the lessons learned skill run before the closure report is signed?▼

No. The closure report must exist and be signed before this skill runs. Validation rule 1 blocks execution and reports that the closure-report prerequisite is not signed yet.

Who approves the lessons learned document?▼

The Project Manager holds final approval authority over the lessons learned document. The Product Owner and Technical Lead review content but do not gate the signature.

What validation checks run before lessons learned sign-off?▼

Nine rules run: signed prerequisites, canonical output path, no placeholder text, no empty sections, correct author field, valid LL-[###] document ID, Project Manager approval row, working cross-references, and English language.