Curie

Skill description

Writes a three-paragraph blameless postmortem for anything that broke or slipped: what happened, why (the real root cause past the symptom), and one concrete system change with an owner. Hard cap, three paragraphs.

Use cases

1. 01

   Engineering team after a SEV2: compress the timeline and descend past the alert miss to the alerting practice that made the miss available.

2. 02

   Founder after a launch slip: isolate whether the delay was scoping, sequencing, or scope creep before committing to the next milestone.

3. 03

   Customer success after a churn event: separate the surface pattern from the system condition so the same failure doesn't recur in a different costume six weeks later.