Agent skill · magnus919
incident-learning
Convert operational incident and near-miss evidence into durable product, engineering, test, evaluation, and governance improvements with verified closure. Separate observed facts from causal hypotheses and unresolved uncertainty; map follow-up work across code, tests, skills, operations, product, and governance; track ownership, verification, and closure for every finding. Do not use to assign blame or produce a generic postmortem template; do not close learning because tickets were created — require evidence the intended change occurred.
What it needs
About 7k tokens when loaded.
What this skill does
Incident Learning Convert operational incidents, near misses, and exercise findings into verified, owned improvements across product, engineering, test, evaluation, and governance domains. This skill owns the learning pipeline — the structured method that takes raw incident evidence and produces durable follow-up work with closure evidence. It does not own incident response, postmortem facilitation, or implementation of follow-up work; it owns the conversion from evidence to verified change. When to use Trigger What it covers --- --- "Convert this incident into follow-up work" Evidence separation, causal ledger, follow-up work map, ownership assignment "What did we learn from this incident?" Learning record with facts, hypotheses, uncertainty, escaped-from mapping "Track this finding to closure" Verification record, closure evidence, follow-up work status "Link this incident to a missing requirement" Escaped-from gap mapping: requirements, monitoring, authority, migration, adoption "Review our incident follow-up closure rate" Learning pipeline audit, unverified closures, stale follow-up work "Process this near-miss" Near-miss learning record, contributing conditions, risk reduction follow-up "Build an incident learning record" Structured record with evidence/inference/uncertainty separation and escaped-from analysis When not to use Assigning blame or conducting a blame-based review. This skill is explicitly blameless. It converts evidence into improvements, not fault into consequences. It contains no blame-assignment process, no "who to blame" field, and no "blameworthy" classification. If you need a postmortem that identifies responsible individuals, this skill will not serve that purpose. Producing a generic postmortem template as the sole output. This skill's artifacts — the incident-learning record, causal/evidence ledger, follow-up work map, and verification and closure record — are the primary deliverables. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/incident-learning