pre-mortem

Compatibility pointer for the canonical premortem skill.

1,237
installs: 0 up / 0 down, score 0.00
votes: 450
repo stars
Updated: less than a month ago
In the catalog since: 7 Oct 2026
From: boshu2/agentops

Get it through your agent npx skills add boshu2/agentops@pre-mortem

Skill instructions

Rendered from the published SKILL.md, 4 lines.

Pre-mortem Compatibility Pointer

Invoke /premortem once and follow its canonical contract.

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "pre-mortem"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository boshu2/agentops
Listing on skills.sh

From boshu2/agentops via skills.sh

Related skills

post-mortem
Compatibility pointer for the canonical postmortem skill.
1,220 installs
build
Plan-then-execute implementation against SPEC.md. Native single-thread loop, no sub-agents. On test or build failure, auto-invokes the backprop skill before retrying — a failed verification always considers whether a new §V invariant would prevent recurrence. Triggers when the user asks to build, implement, execute the spec, or tackle a specific §T task (`build §T.3`, `build --next`, `implement next task`, `run the build`). Expects SPEC.md to exist; if not, defers to the spec skill.
2,681 installs
challenge
Pre-mortem plan analysis. Imagine the plan failed 12 months from now and work backwards to find the weaknesses. Surfaces assumptions, dependencies, and execution risks before committing resources. Use when before significant resource commitment, before presenting to a board or investors, when feedback has been one-sidedly positive, or when there is pressure to move fast and figure it out later.
1,438 installs
post-mortem
Write the canonical engineering record of a fixed bug — root cause, mechanism, fix, validation, and how it slipped through. Engineer-audience, code identifiers welcome. Use after a debug session lands a fix, before closing the ticket. Trigger on /post-mortem, when the user says "write the post-mortem / postmortem / RCA / root cause analysis", "document this fix", "write up the root cause", "close out this bug with a writeup", or hands you a fixed-and-validated bug and asks for the writeup.
4,666 installs
pr-prep
Prepare PR commits and body. Triggers: "pr-prep", "pr prep", "prepare pr commits and body.".
1,115 installs