skills.rest
parcadei
parcadeiCOMMUNITY
Explore all skills by this author →
GitHub

premortem

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

3.9k|296|Updated Dec 23, 2025
Search Tags:#code review#project planning#proactive#failure modes#risk analysis#premortem
One-click install
npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill premortem-parcadei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: premortem
Source: https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/premortem
Command: npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill premortem-parcadei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps proactively identify potential risks and failure points in plans, designs, or implementations before they can cause significant problems.

Core Features & Use Cases

  • Structured Risk Analysis: Applies frameworks like Shreyas Doshi's to categorize risks (Tiger, Paper Tiger, Elephant).
  • Verification Focus: Emphasizes verifying potential risks to avoid false alarms and ensure actionable insights.
  • Workflow Guidance: Provides detailed steps for quick (plans, PRs) and deep (pre-implementation) analysis.
  • Use Case: Before starting a major coding feature, run a deep pre-mortem to uncover potential integration issues, scalability concerns, or security vulnerabilities that could derail the project.

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
What is a premortem analysis in software project planning?▼

A premortem analysis is a proactive risk assessment that identifies potential failure modes in project plans or code implementations before development begins. It categorizes verified risks into Tiger, Paper Tiger, and Elephant types to prevent false alarms.

How do I identify failure modes before starting a major coding feature?▼

Run a deep pre-implementation premortem to systematically uncover potential integration issues, scalability concerns, and security vulnerabilities. The analysis enforces verification steps to distinguish real threats from false alarms before you write code.

Can I run a quick risk analysis on a pull request before merging?▼

Yes, you can run a quick premortem assessment specifically designed for plans and pull requests. It provides rapid workflow guidance to identify immediate risks and failure points in code reviews without a full deep review.

What is the best way to categorize project risks and avoid false alarms?▼

Use Shreyas Doshi's structured risk analysis framework to categorize threats into Tiger, Paper Tiger, and Elephant types. This approach enforces verification steps to ensure actionable insights and filter out false alarms during risk analysis.

When should I not use a proactive premortem for risk analysis?▼

A proactive premortem may be unnecessary for trivial code changes or tasks with minimal integration impact. It is designed for identifying complex failure modes in project plans, designs, and major implementations where structured verification provides value.

Related Skills

Explore More Software Engineering Skills→
mikkeymoomikkeymoo
1

mm-premortem

Identify potential project failure modes through structured risk analysis.

Community
Intermediate
scooter-lacroixscooter-lacroix
8

premortem

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

Community
Advanced
JesusFilmJesusFilm
25

lfg

Coordinate planning, implementation, review, and browser testing in engineering workflows.

Official
Advanced
lozitlozit
2

premortem

Simulate a post-mortem analysis to identify and rank project risks.

Community
Intermediate