lessons-learned-repository
Capture, categorize, and retrieve project lessons learned for organizational learning
Best use case
lessons-learned-repository is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Capture, categorize, and retrieve project lessons learned for organizational learning
Teams using lessons-learned-repository should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/lessons-learned-repository/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How lessons-learned-repository Compares
| Feature / Agent | lessons-learned-repository | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Capture, categorize, and retrieve project lessons learned for organizational learning
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Lessons Learned Repository ## Overview The Lessons Learned Repository skill provides comprehensive capabilities for capturing, categorizing, storing, and retrieving project lessons learned. It supports organizational learning by making past experiences searchable and actionable for current and future projects. ## Capabilities ### Lesson Capture - Capture lessons using structured templates - Support positive and negative lessons - Document context, impact, and recommendations - Link lessons to specific project phases and deliverables - Capture lessons from retrospectives and reviews ### Categorization - Categorize by project phase and knowledge area - Tag by project type and industry - Classify by outcome (success, failure, improvement) - Link to root causes and contributing factors - Associate with process areas and standards ### Search and Retrieval - Search and retrieve relevant lessons for new projects - Recommend applicable lessons based on project context - Support full-text and faceted search - Filter by relevance, recency, and applicability - Generate lesson briefings for project teams ### Analysis and Reporting - Generate lessons learned reports - Analyze patterns across project history - Calculate lesson implementation rate - Identify recurring issues and successes - Track lesson application outcomes ## Usage ### Input Requirements - Lesson description and context - Project and phase information - Categorization attributes - Recommendations and actions - Optional: Supporting evidence and artifacts ### Output Deliverables - Lessons learned register - Search/retrieval results - Pattern analysis report - Recommended lessons for new projects - Lessons implementation tracking ### Example Use Cases 1. **Project Closure**: Capture final lessons learned 2. **Project Kickoff**: Retrieve relevant historical lessons 3. **Process Improvement**: Analyze lesson patterns 4. **Training Development**: Compile lessons for training ## Process Integration This skill integrates with the following processes: - Lessons Learned and Knowledge Management - Sprint Retrospective Facilitation - benefits-realization.js - Project Charter Development ## Dependencies - Knowledge base infrastructure - Search/retrieval engine - Pattern analysis utilities - Recommendation algorithms ## Related Skills - SK-015: Retrospective Facilitator - SK-008: Stakeholder Matrix Generator - SK-011: Benefits Tracking Dashboard
Related Skills
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.
issue
Run an issue-centric Babysitter workflow.