lessons-learned

Capture project discoveries into a structured LESSONS.md file after phase completion.

66|3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/lgbarn/shipyard --skill lessons-learned
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lessons-learned
Source: https://github.com/lgbarn/shipyard/tree/main/skills/lessons-learned
Command: npx skills add https://github.com/lgbarn/shipyard --skill lessons-learned

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams capture and preserve valuable discoveries after a phase completes, reducing loss of knowledge and accelerating future work.

Core Features & Use Cases

  • Structured lesson capture: guided prompts ensure consistent documentation of outcomes, decisions, and improvements.
  • Centralized repository: stores lessons in .shipyard/LESSONS.md and can surface insights in CLAUDE.md for future agents.
  • Reuse and auditing: enables learning from past phases to improve planning, development, and shipping.

Quick Start

Use the lessons-learned skill to capture discoveries after a phase completes and prepend them to .shipyard/LESSONS.md for future reuse.

Frequently Asked Questions about lessons-learned

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

FAQPage Schema
How do I capture lessons learned after a project phase completes?

To capture lessons learned after a project phase, use guided prompts to document outcomes, decisions, and improvements, storing them in a centralized LESSONS.md file for future reuse.

What is the best way to document a post-mortem for reuse across future projects?

Documenting a post-mortem for reuse involves extracting patterns and decisions into a structured LESSONS.md format, ensuring project discoveries are codified for future planning and development.

How does a lessons learned repository update CLAUDE.md for future agents?

A lessons learned repository updates CLAUDE.md by optionally surfacing extracted insights from post-phase reviews, making project knowledge directly available to future agents.

Do I need dependencies or components to structure my project knowledge management?

You do not need any dependencies or components to structure project knowledge management; the skill operates independently to enforce documentation formats and capture discoveries.

When should I run a post-phase review to extract reusable patterns?

You should run a post-phase review to extract reusable patterns after a phase completes and before shipping, ensuring discoveries are captured while context is fresh.