Creates a structured lessons learned entry for organizational memory. Use after an incident, a completed project, or a significant learning to record knowledge for future teams and initiatives. Distinct from iterate-retrospective, which facilitates the team ceremony; this skill writes the durable lessons entry that outlives it.
NewMaintained
Automatic
◆Product Management pack
Last verified 8/18/2026
What it changes
Passed 7 of 22 test cases with the skill, and 15 of 22 without it.
Without skill67%
With skill33%
Checks it passed that the model alone missed
The response includes organizational metadata fields containing author, date, status, and target audience.
1 fixed19 passed either way0 still failing2 broke
Pass-rate lift
-33 pp
Tokens
+35%
Agent turns
0%
Response time
+9%
Model gemini-3.6-flashMeasured 8/18/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
We are documenting our findings after migrating from monolithic REST APIs to gRPC services across our backend systems. Produce a lessons log document that starts with the complete organizational metadata section.
What was checked, without and with the skill
Checked
Without skill
With skill
The response includes organizational metadata fields containing author, date, status, and target audience.
Missed
Passed
case-08 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md64 lines3 files
Lessons Log
A lessons log entry captures significant learning from projects, incidents, or experiences in a format that's useful to future teams who weren't there. Unlike retrospectives (which focus on team improvement), lessons logs focus on organizational knowledge that transcends individual teams.patterns, anti-patterns, and hard-won wisdom.
When to Use
After completing a significant project or initiative
Following a major incident, outage, or failure
When you realize something important that others should know
After discovering a pattern that keeps recurring
When experienced team members leave (capture their knowledge)
During post-mortems to preserve learnings
When NOT to Use
You are facilitating the team ceremony itself -> use iterate-retrospective; this skill banks the durable entry that outlives it
You are deciding whether to change direction based on results -> use iterate-pivot-decision
The learning is an experiment readout -> use measure-experiment-results first, then bank the transferable lesson here
You are updating stakeholders on what was learned -> use foundation-stakeholder-update
Instructions
When asked to create a lessons log entry, follow these steps:
Choose a Descriptive Title
Write a title that someone searching for this topic would find. Include keywords that describe the situation and the learning. Avoid generic titles like "Project X lessons."
Provide Context
Explain the situation fully enough that someone who wasn't there can understand it. Include the project, timeline, team, and any relevant constraints. Future readers need this context to assess applicability.
Describe What Happened
Write a factual account of what occurred. Be specific about actions taken, decisions made, and outcomes observed. Avoid blame.focus on events and systems.
Extract the Lesson
Articulate what you learned clearly. The lesson should be actionable.something others can apply. Distinguish between what you observed and your interpretation of why it matters.
Formulate Recommendations
Provide specific guidance for future teams facing similar situations. What should they do? What should they avoid? What questions should they ask?