What problem does it solve? When an incident, failed launch, or missed deadline happens and you are the only person responsible, there is no team to run a retrospective with. This Skill turns a recent failure into a short, structured postmortem that produces one or two concrete systemic changes instead of vague self-blame. ## Core Features & Use Cases - Five-Section Structure: What happened, impact, timeline, root causes via 5 Whys, and at most two changes with owner, due date, and verification method. - Strict Word Limits: Total output capped at 350 words to force decisions rather than lengthy reports. - No-Blame Accountability Framing: Steers root causes toward process, automation, and alerts rather than personal fault or external excuses. - Use Case: After a Friday deploy broke your signup flow for six hours and cost 40 trial signups, use this Skill to draft a postmortem that identifies the missing 500-rate alert and produces a deploy-time blocking rule. ## Quick Start Ask the AI to run a solo postmortem on the incident where your last launch failed, describing what happened and what it cost.
