pre-mortem

Analyze project risks and generate mitigation strategies using the pre-mortem methodology.

Updated May 20, 2026
One-click install
npx skills add https://github.com/MilUX-Ltd/foothold --skill pre-mortem-milux-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-mortem
Source: https://github.com/MilUX-Ltd/foothold/tree/main/foothold/template/Skills/pm-skills/pre-mortem
Command: npx skills add https://github.com/MilUX-Ltd/foothold --skill pre-mortem-milux-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you identify and prepare for potential issues before executing a plan or project, ensuring smoother outcomes and reducing uncertainty.

Core Features & Use Cases

  • Risk Analysis: Identify real and potential problems before execution.
  • Risk Classification: Sort risks into 'Tigers' (real), 'Paper Tigers' (overblown), and 'Elephants' (unspoken).
  • Action Planning: Generate action plans for 'Tigers' with mitigation strategies.
  • Use Case: Run a pre-mortem for a software project to identify technical and operational risks that could impact success.

Quick Start

Use the pre-mortem skill to run a pre-mortem analysis for the 'software project' plan.

Frequently Asked Questions about pre-mortem

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

FAQPage Schema
How do I identify potential risks before executing a project plan?

A pre-mortem analysis anticipates project issues by assuming failure and working backward to identify potential risks before execution begins. This methodology classifies identified problems into 'Tigers', 'Paper Tigers', and 'Elephants' to ensure smoother project outcomes and reduce uncertainty.

What is the difference between Tigers, Paper Tigers, and Elephants in risk classification?

In risk classification, 'Tigers' represent real problems, 'Paper Tigers' are overblown risks, and 'Elephants' are unspoken issues. Sorting potential risks into these categories helps focus mitigation efforts strictly on real threats during strategic planning.

How do I generate mitigation strategies for a software project?

To generate mitigation strategies for a software project, run a pre-mortem analysis to identify technical and operational risks that could impact success. The process creates targeted action plans specifically for classified 'Tiger' risks to mitigate potential problems before execution.

Can I use pre-mortem risk analysis for strategic planning workflows?

Yes, pre-mortem risk analysis applies directly to strategic planning and project management workflows. The methodology requires structured planning and analytical capabilities to anticipate and mitigate risks in your upcoming plans, projects, or business initiatives before execution.

What is the best way to prepare for unspoken risks in business analysis?

The best way to prepare for unspoken risks is through pre-mortem analysis, which classifies hidden issues as 'Elephants'. This methodology ensures these unspoken problems are explicitly identified and addressed during strategy planning rather than surfacing unexpectedly during project execution.

When should I not use pre-mortem methodology for risk analysis?

Pre-mortem methodology is not ideal for reactive troubleshooting or operational tasks lacking structured planning capabilities. Since it focuses on identifying potential problems before execution, it is unsuitable for post-mortem analysis after a project has already failed or encountered issues.