lessons-learned

Name: lessons-learned
Availability: InStock
Author: CivicActions

Write structured lessons-learned reflection notes after completed tickets, sprints, or project phases.

2|Updated May 24, 2026

Search Tags:#documentation #knowledge management #retrospective #post-mortem #process improvement #reflection

Ready to run

npx skills add https://github.com/CivicActions/ai-runbook-jh --skill lessons-learned-civicactions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lessons-learned
Source: https://github.com/CivicActions/ai-runbook-jh/tree/main/skills/lessons-learned
Command: npx skills add https://github.com/CivicActions/ai-runbook-jh --skill lessons-learned-civicactions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of losing valuable project knowledge by providing a structured, consistent way to reflect on completed work, ensuring that lessons learned are captured, documented, and applied to future tasks.

Core Features & Use Cases

Structured Reflection: Guides the user through a standardized retrospective process covering successes, failures, root causes, and future improvements.
Context-Aware Documentation: Integrates with project-specific contracts to ensure reflections are stored in the correct location and follow established team voice and attribution conventions.
Use Case: After finishing a complex ticket, use this skill to generate a reflection note that identifies why a specific bug occurred and how to adjust the team's testing strategy to prevent it in the future.

Quick Start

Invoke the lessons-learned skill to generate a reflection note for the recently completed ticket PROJ-1234.

Frequently Asked Questions about lessons-learned

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

FAQPage Schema

How do I document lessons learned after finishing a project phase?▼

Capturing retrospective insights requires generating a structured reflection note that covers successes, failures, root causes, and future process improvements. This approach ensures valuable project knowledge is consistently documented and applied to future development tasks.

What is a post-mortem reflection note and when should I write one?▼

A post-mortem reflection note is a structured retrospective document created after completing a ticket, sprint, or project phase. You should write one when you need to capture process improvements and prevent recurring bugs in professional software development workflows.

How do I create a structured retrospective for a completed sprint?▼

Create a structured retrospective by invoking the reflection process on completed work, which guides you through analyzing successes and root causes. The output is a formatted lessons-learned note stored in your configured knowledge base location.

Do I need project-specific contract files for knowledge management documentation?▼

Yes, you need access to project-specific contract files for knowledge management documentation. These contracts determine the output formatting, voice configuration, and knowledge base storage locations required to properly save the reflection notes.

What's the best way to capture process improvements from a complex ticket?▼

The best way to capture process improvements from a complex ticket is using a standardized retrospective process that identifies why specific bugs occurred. This generates a reflection note detailing how to adjust testing strategies to prevent future issues.