Lessons Learned
0This skill helps users manage project lessons effectively, ensuring all lessons learned during tasks are captured and evaluated. Ideal for project managers and teams aiming to enhance learning from their work.
000Updated 2mo ago
Project Management
Quick InstallView Source
$ npx skills add https://github.com/shihyuho/skills --skill lessons-learnedOverview
About This Skill
The README provided does not contain a 'Lessons Learned' skill. The available skills listed include ADR (Architecture Decision Records), writing agents, SDK management, code coverage, review briefing, TL;DR generation, learning tools, rephrasing utilities, kickoff workflows, and artifact anatomy—but no lessons learned management skill is documented. Without official README documentation, accurate technical content cannot be provided.
How to Use
Install using the command: `$ npx skills add https://github.com/shihyuho/skills --skill lessons-learned`
Use Cases
Run recall before starting implementation tasks.
Capture lessons during task correction.
Evaluate lessons at the end of tasks.
Tags
Setup & Installation
Quick Install
Terminal
$ npx skills add https://github.com/shihyuho/skills --skill lessons-learnedAlternative Install (Git Clone)
git clone https://github.com/shihyuho/skillsRequirements
- Claude Code or compatible AI agent
Quick Start Guide
1
Install the Skill
Copy the install command above and run it in your terminal.
2
Open Your AI Agent
Launch Claude Code, Cursor, or your preferred AI coding agent.
3
Try It Out
Use the prompt template or examples below to test the skill.
4
Customize
Adapt the skill to your specific use case and workflow.
Usage Examples
Prompt Template
Act as a project lessons learned facilitator. Help me capture, document, and evaluate key lessons from [PROJECT_NAME] in [INDUSTRY]. Focus on successes, failures, and actionable improvements. Structure the output as a lessons learned report with sections for: 1) What happened, 2) Why it happened, 3) What we learned, and 4) Action items. Include specific examples from [DATA] or [TEAM_MEMBERS].
Example Output
### Lessons Learned Report: Q3 2024 E-commerce Platform Migration #### 1. What Happened - **Success**: The migration from legacy monolithic architecture to microservices was completed 2 weeks ahead of schedule, with zero downtime during the transition. - **Challenge**: The team underestimated the complexity of data synchronization between old and new systems, leading to 3 minor data inconsistencies reported by customers. #### 2. Why It Happened - **Success Factor**: Weekly cross-functional sync meetings (led by Sarah from DevOps) ensured alignment between development, QA, and operations teams. - **Challenge Cause**: The data migration script (developed by the backend team) did not account for edge cases in order statuses, as identified in [PROJECT_TRACKER]. #### 3. What We Learned - **Process Improvement**: Implement a dedicated data validation sprint post-migration to catch discrepancies early (estimated 20% reduction in post-launch issues). - **Team Insight**: The DevOps team’s proactive monitoring tools (e.g., Prometheus alerts) were critical in identifying performance bottlenecks during the migration. #### 4. Action Items - [ ] Schedule a retro with the backend team to address data sync gaps (Owner: Alex, Due: Oct 15). - [ ] Update the migration playbook to include a data validation checklist (Owner: Priya, Due: Oct 20). **Next Steps**: Share this report with the leadership team and schedule a workshop to refine the migration process for Q4 projects.
Find the right skills for your stack
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan