operational-learning
Turn a resolved incident, drill, audit, or approved component or alert change into durable knowledge (service and alert cards, runbook dispositions), and answer ownership questions from those records. Triggers: 'which team owns payments and how do I page them', 'what depends on ledger', 'capture durable operational lessons', 'apply the operational-learning closeout'. Direct KB writing belongs to scribe, which selects closeout mode and applies this skill; active incidents route to incident-investigation, alert design to observability-engineer, and fleet prompt failures to agent-engineer. Retrospective write-ups use postmortem.
Pinned to revision 8d7ecda1ebc6, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/operational-learning/SKILL.md
- skills/operational-learning/assets/alert-card-template.md
- skills/operational-learning/assets/knowledge-index-template.md
- skills/operational-learning/assets/service-card-template.md
- skills/operational-learning/references/disposition-policy.md
Every link opens the file at its source, pinned to the revision this page describes.