learn-and-improve
Learn and Improve
The Act phase of PDCA: turn finished work into reusable knowledge. This skill exists because most "lessons learned" stages are shallow — a vague "what went well / what didn't" list that captures lessons but never applies them. This skill makes retrospective and sediment a disciplined, depth-bearing practice.
Why this skill exists
Across PDCA-style fix workflows, the review stage was often an afterthought — each host wrote a shallow inline version, nobody imported real methodology, and the same lessons got captured then forgotten. Compare solution-review, which is a deep independent skill for phase 3 (citing FMEA / SRE PRR / CBAM). This skill is the equivalent for the Act stage: deep, methodology-anchored, reusable.
The core disease it treats is "captured but not applied" — lessons written into a doc and never retrieved. PMI identifies this as the dominant failure of lessons-learned programs. So retrieval/effectiveness validation is a first-class step here, not an afterthought (the Retrieve step of the lessons-learned 5-step: Identify → Document → Analyze → Store → Retrieve).
When to use
- Standalone: the user finished work and wants to reflect — "复盘一下这次", "做个回顾总结", "what did we learn from this".
- Integrated: a PDCA host reaches its review or closeout stage and loads this skill via frontmatter
dependencies.
The trigger phrases in the description govern both paths.