| name | lessons-learn |
| description | Record and maintain Lessons in MEMORY.md after a problem is solved or the user confirms success. Use when capturing a new lesson, moving lessons through the pipeline, or updating Session State to reflect learning. |
Lessons Learn
Goal
Capture durable learning from a solved problem and keep the Memory pipeline consistent.
When to use
Use this skill when:
- The user confirms a fix worked (e.g., “works”, “fixed”, “отлично”).
- A non‑obvious bug or root cause was discovered.
- A recurring pattern should be turned into a protocol.
Workflow
- Open
MEMORY.md(repo root). - Append a new Lesson to
## 🆕 Lessons (Inbox)using this template:
### <YYYY-MM-DD> <Short title>
**Problem:** <what was broken>
**Attempts:** <what was tried, if any>
**Solution:** <what fixed it>
**Why it worked:** <causal explanation>
**Principle:** <one-sentence rule for the future>
If 3+ related lessons exist, create a Short‑Term entry:
- Move the related lessons (or summarize them) into
## 🔄 Short-Term Memory. - Write a common pattern and an emerging principle.
- Move the related lessons (or summarize them) into
If a principle is stable, promote it to
## 💎 Long-Term Memoryas a protocol:- Format: Context → Protocol → Reasoning.
Update Session State only if it affects the current task.
Output expectations
- Report exactly what you recorded or moved.
- If you did not write a lesson, say why.