lessons-learned

Capture structured learning entries with YAML frontmatter after workflow phases.

3|2|Updated Dec 16, 2025

Search Tags:#documentation #reflection #lessons #phase-review #learning-entry

Ready to run

npx skills add https://github.com/jakekausler/claude-code-workflow --skill lessons-learned-jakekausler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lessons-learned
Source: https://github.com/jakekausler/claude-code-workflow/tree/main/skills/lessons-learned
Command: npx skills add https://github.com/jakekausler/claude-code-workflow --skill lessons-learned-jakekausler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that noteworthy events from Design, Build, Refinement, or Finalize phases are captured as structured learning entries, turning experiences into actionable guidance.

Core Features & Use Cases

Trigger-driven learning entries: Evaluate the phase outcomes using defined triggers and generate a standardized Learning Entry when any trigger applies.
Structured format: Each entry includes date, repository, epic, stage, phase, category, and an actionable Future Guidance section.
Local archival: Stores entries under ~/docs/claude-learnings with timestamped filenames for easy retrieval.

Quick Start

After finishing a phase, run this skill to assess triggers and generate the learning entry accordingly.

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 during a project phase?▼

To document lessons learned, this skill captures structured learning entries after Design, Build, Refinement, or Finalize phases. It evaluates trigger conditions and writes standardized YAML frontmatter and Markdown notes to a local archive for future reference.

What is the best way to capture phase reflections for future workflows?▼

Capturing phase reflections is best handled by generating standardized Markdown entries with YAML frontmatter. This approach records the date, repository, epic, stage, and phase alongside actionable future guidance in a local learning archive.

How do I record noteworthy events from an epic-stage-workflow phase?▼

To record noteworthy events from an epic-stage-workflow phase, run this skill after finishing the phase. It assesses defined triggers and automatically generates a timestamped learning entry in your local documentation folder.

Do I need any external dependencies to archive learning entries locally?▼

No external dependencies are required to archive learning entries locally. The skill independently writes structured YAML frontmatter and Markdown body files directly to the ~/docs/claude-learnings directory on your system.

Can I use structured documentation for retrospective analysis across multiple phases?▼

Yes, structured documentation supports retrospective analysis across multiple phases. Each entry includes standardized fields like category, phase, and an analyzed flag, making it easy to retrieve and review past experiences from the local archive.

When should I not use automated phase-review documentation?▼

Automated phase-review documentation should not be used if your workflow lacks distinct Design, Build, Refinement, or Finalize phases. The skill relies on these specific epic-stage-workflow phases to trigger learning entry generation effectively.