skills.rest
scooter-lacroix
scooter-lacroixCOMMUNITY
Explore all skills by this author →
Website𝕏@scooter_lacroixGitHub

premortem

Identify and categorize project risks as Tiger, Paper Tiger, or Elephant.

8|1|Updated Jan 4, 2026
Search Tags:#planning#project management#code review#failure modes#risk analysis#premortem
One-click install
npx skills add https://github.com/scooter-lacroix/Maestro --skill premortem-scooter-lacroix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: premortem
Source: https://github.com/scooter-lacroix/Maestro/tree/main/maestro/skills/planning/premortem
Command: npx skills add https://github.com/scooter-lacroix/Maestro --skill premortem-scooter-lacroix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps proactively identify potential failure points in plans, designs, or code before they become critical issues, leading to more robust and reliable outcomes.

Core Features & Use Cases

  • Structured Risk Analysis: Systematically questions plans and designs to uncover hidden threats.
  • Failure Mode Identification: Categorizes risks into 'Tiger' (clear threat), 'Paper Tiger' (looks threatening but okay), and 'Elephant' (unspoken concern).
  • Verification Process: Mandates rigorous verification to avoid false positives and ensure identified risks are genuine.
  • Use Case: Before implementing a new feature, run a deep pre-mortem to identify potential technical, integration, or process risks, ensuring mitigation strategies are in place.

Quick Start

Run a quick pre-mortem analysis on the current plan.

Frequently Asked Questions about premortem

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

FAQPage Schema
How do I identify potential failure modes in a project plan before implementation?▼

To identify failure modes in a project plan, perform a structured risk analysis using a premortem checklist to categorize threats into Tigers, Paper Tigers, or Elephants before implementation begins.

What is the difference between a Tiger, Paper Tiger, and Elephant in risk analysis?▼

In risk analysis, a Tiger is a clear threat, a Paper Tiger appears threatening but is ultimately safe, and an Elephant represents an unspoken concern that must be addressed before it materializes.

How do I run a pre-implementation review to uncover hidden technical risks?▼

Run a pre-implementation review by systematically questioning your design through a verification process to uncover hidden technical risks and ensure mitigation strategies are in place.

Can I use a premortem analysis for pull request and code review validation?▼

Yes, you can apply premortem analysis to PR analysis and code review validation to proactively identify potential failure points and ensure code reliability before merging.

Why does my project risk analysis produce false positives during verification?▼

Project risk analysis produces false positives when verification is skipped, which is why a rigorous verification process is mandated to ensure identified threats are genuine.

What's the best way to categorize unspoken concerns during project planning?▼

The best way to categorize unspoken concerns during project planning is to use a structured premortem checklist that systematically identifies and classifies risks to ensure robust outcomes.

Related Skills

Explore More Software Engineering Skills→
mikkeymoomikkeymoo
1

mm-premortem

Identify potential project failure modes through structured risk analysis.

Community
Intermediate
WcofWcof
1

pm-premortem

Run a pre-mortem on PMContext to classify launch risks and validate assumptions.

Community
Advanced
lucascarolucascaro

gc-sweep

Detect and correct code deviations against golden-principle guidelines in repositories.

Community
Intermediate
parcadeiparcadei
3.9k

premortem

Identify potential failure modes and risks in project plans using structured analysis.

Community
Advanced