Individual skill

premortem

Find how a rollout plan could fail before committing to it. Use when: asked what could go wrong or to poke holes in a plan.

plugin/skills/premortem/SKILL.md

Read pinned source

Source commit 7547dab37a18f36def54b25e0c81eb39ef9dffef

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 5, 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)
453
Repository last updated
Nov 8, 2026
License
Apache-2.0

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

Premortem is an optional plan-challenge strategy. It asks one fresh context to
identify concrete ways the resolved bead or caller intent could fail before implementation.
It is not part of the required RPI sequence and does not authorize readiness.
[Plan's shared challenge method](../plan/references/challenge.md) owns optional
exchange, dispatch and stopping rules; when no fresh context can be started,
step 2's labelled self-judged fallback replaces its no-stand-in rule here.
Premortem owns the three checks below. Neighbours: general advice is
[Review](../review/SKILL.md), acceptance of a finished change is
[Validate](../validate/SKILL.md), and several independent views are
[Council](../council/SKILL.md).

Run the checks in this order and report findings in the same order: a finding