premortem-protocol

Runs a structured five-phase premortem risk analysis on plans and kanban artifacts.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/soli92/soli-projects --skill premortem-protocol-soli92
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: premortem-protocol
Source: https://github.com/soli92/soli-projects/tree/main/.cursor/skills/premortem-protocol
Command: npx skills add https://github.com/soli92/soli-projects --skill premortem-protocol-soli92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams commit to plans, epics, and design decisions without systematically stress-testing what could go wrong, discovering risks only after failure. This Skill applies prospective hindsight to surface failure modes, hidden assumptions, and early warning signs before a decision becomes irreversible. ## Core Features & Use Cases - Five-phase protocol: Context Gathering with a fail-loud minimum bar, Frame Setting with a verbatim failure statement, Raw Premortem across five categories (Execution, External, People, Technical, Assumptions), Parallel Deep-Dives via up to 8 sub-agents, and a Synthesis phase. - Structured Risk Registry: Outputs a 9-column risk table classifying risks as Tigers, Paper Tigers, or Elephants, with urgency levels, calibration warnings, a revised plan, and a pre-launch checklist. - Opt-in and non-destructive: Triggered only by explicit invocation, never auto-applies changes to epics, user stories, or tasks, and logs metadata-only telemetry to an episodic memory file. - Use Case: Before promoting a high-impact epic from draft to review, run a premortem on it to receive a narrative of the most likely failure, the hidden assumption behind it, and a checklist of mitigations to discuss with stakeholders. ## Quick Start Ask the AI to run a premortem on a specific epic, user story, task, wiki page, or free-text plan description, optionally specifying a timeframe such as six months.

Frequently Asked Questions about premortem-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a premortem analysis on a project plan?▼

Invoke the premortem explicitly with a target: a kanban artifact ID (EP/US/TSK), a wiki page path, or a free-text plan description. The skill gathers context, frames the failure as having already happened, then generates and classifies risks.

What is a premortem and when should I use one?▼

A premortem is a prospective hindsight exercise that assumes a plan has already failed and works backward to explain why. Use it before high-stakes, still-reversible decisions like epic promotion, architecture migrations, or major version bumps.

What are Tigers, Paper Tigers, and Elephants in risk classification?▼

They are the three tiers of the output risk taxonomy: Tigers are real urgent threats (with Launch-Blocking, Fast-Follow, or Track urgency), Paper Tigers are fears that turn out harmless, and Elephants are known risks nobody discusses.

Does the premortem skill modify my epics or tasks automatically?▼

No. The revised plan and pre-launch checklist are always suggestions emitted in chat. The body of epics, user stories, and tasks stays unchanged, and frontmatter edits are only suggested, never auto-applied.

Why does the premortem refuse to proceed on my input?▼

The skill enforces a minimum context bar: it must know what you are doing, for whom, and what success looks like. If deduction from the artifact fails, it asks one question at a time and fails loudly rather than producing a sanitized output.

When should I not use a premortem?▼

Avoid it for generic code review, factual questions, creative brainstorming, or decisions already irrevocably made. The premortem is retrospective and pre-fact, so it wastes effort when no course correction is possible.