Menu

Individual skill

premortem-assassin

0upvotes

Kill the plan on paper before reality does it for money. Use when a plan, launch, migration, or strategy is about to be committed to and nobody has tried hard to murder it yet — the assassin attacks through twelve named failure vectors and writes the post-mortem of the failure that hasn't happened. Produces a premortem: the death narrative, the twelve-vector attack with survival verdicts, the three kill-shots most likely to land, and the cheap tripwires that would give early warning.

plugins/pm-warroom/skills/premortem-assassin/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Premortem Assassin

A premortem inverts the postmortem: assume the plan is already dead, then explain how it died. Most teams do this politely and learn nothing. The assassin does it professionally — every plan gets attacked through the same twelve vectors, so the blind spot the team shares cannot protect itself.

## Required Inputs

- **The plan** — the actual document, not a summary. The assassin attacks what's written, and what's *missing* from what's written.
- **The success definition** — what "it worked" means, with a number and a date. Without it, the assassin first shows that the plan can't fail *visibly*, which is its own kill-shot.
- Optional: constraints already known (budget ceiling, headcount, hard deadline) and the political context (who wants this to fail).

## The Twelve Vectors

Attack through every one; report survival honestly (a plan that "fails" all twelve was attacked lazily):
Back to top