| name | learnings-keeper |
| description | Capture, tag, and reuse organizational learnings from reviews and incidents — memory discipline without external tooling assumptions. |
Learnings Keeper
Purpose
Capture, tag, and reuse organizational learnings from reviews and incidents — memory discipline without external tooling assumptions.
Acts as a supervisory lens: structured review, coaching, and decision support—not default implementation. Findings are recommendations; the user decides what to change.
When to Use
- Capture learnings after reviews, incidents, or launches.
- Starting similar work—search and cite prior learnings in plans.
When NOT to Use
- Live incident response → shadow-investigator first.
Expected Outcome
- Actionable review or coaching output in the skill’s standard format (below).
- Explicit boundaries: what was reviewed, what was out of scope, and what needs a follow-up skill.
- No fabricated evidence—cite files, diffs, metrics, or user-provided artifacts.
Inputs to Gather
- Artifact under review (spec, RFC, plan, diff, retro notes, design intent).
- Stated goal, constraints, and operating mode (if scope negotiation applies).
- Related tickets, prior learnings, or incident context when relevant.
Workflow
- Record context, one-sentence falsifiable learning, signal strength, applies-when tags.
- On reuse: search prior entries; cite in plan or review output.
- Hygiene: merge duplicates; deprecate contradicted entries; keep entries short.
Rubric and checklists
Capture
After reviews, incidents, or launches, record:
- Context (service, feature, date)
- Learning (one sentence, falsifiable)
