DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to draft a blameless postmortem with the Codex plugin with Sepia

Write a postmortem that names mechanisms, timestamps, and owned action items.

  • Content
  • Intermediate
  • 30 minutes
  • From the README
  • Codex

Who it is forAn engineer on call who must write an incident postmortem from timeline notes and wants the venue rules applied.

The problemPostmortem drafts often blame people, skip dead ends, or leave action items unowned.

The outcomeA first draft that is blameless toward people, direct about mechanisms, and lists timestamps and owned action items.

What you need first

  • An Agent Skills-compatible agent, or Claude Code or Codex for the native plugin packaging
  • The complete sepia plugin package installed, since the README says standalone wrapper installation is unsupported
  • A draft file or pasted text to review

Steps

  1. Install the complete Sepia plugin package for Codex.
  2. Use the install route described under Install in the README to add the plugin. (inferred, check the README)
  3. Run $sepia-write with the incident timeline and the postmortem brief as input.
  4. Run $sepia-review on the result to check it against the postmortem rules.
  5. Add owners and dates to any action item the review flags as unowned.

Prompt for your agent

Using the sepia repo, run its write operation to draft a postmortem from <timeline notes file>. Expected output: a postmortem with timestamps, dead ends, and owned action items. Verify that every timestamp matches the timeline notes.

Caveat. The postmortem rules are one domain in the professional rule set, and the README gives no example postmortem to check output against.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page