Lessons were structured around recording "what was done" (Resolution) and "what remains" (Follow-up) — essentially incident reports. They should instead drive concrete improvements: skill updates, automated checks, or code refactors.

usethis-lesson-create SKILL.md (v1.1 → v1.2)

• Intro: Explicitly frames lessons as proposals for lasting improvement, not records of one-off fixes
• Procedure: New step 4 "Propose a concrete action" with three categories in preference order: skill update → automated check → code refactor
• Template: Replaced Resolution + Follow-up sections with single Recommended action section requiring categorized concrete improvements
• Root cause example: Added Action row to the 5-Whys table

Old template tail:

## Resolution
<How the problem was resolved in this instance...>

## Follow-up
<Any work that remains...>

New:

## Recommended action
<One or more concrete improvements to prevent this class of problem from recurring.
Each action should fall into one of these categories:
- **Skill update:** which skill to update and what guidance to add or revise.
- **Automated check:** a new or improved linting rule, prek hook, or CI check to add.
- **Code refactor:** a structural change that makes the mistake impossible or harder.>

AGENTS.md

• Updated Lessons section to mention the action-oriented requirement