skills.rest
avelikiy
avelikiyCOMMUNITY
Explore all skills by this author →
GitHub

pre-mortem

Identify potential project failure risks using a structured 5-step pre-mortem analysis.

75|13|Updated Apr 5, 2026
Search Tags:#project management#software engineering#project failure#risk identification#pre-mortem analysis
One-click install
npx skills add https://github.com/avelikiy/great_cto --skill pre-mortem-avelikiy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-mortem
Source: https://github.com/avelikiy/great_cto/tree/main/skills/pre-mortem
Command: npx skills add https://github.com/avelikiy/great_cto --skill pre-mortem-avelikiy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps identify potential failures in a project early on by imagining what could go wrong and analyzing the causes.

Core Features & Use Cases

  • Risk Identification: Encourages concrete risk identification, not vague lists.
  • Step-by-Step Analysis: Provides a structured 5-step process to analyze the potential causes of project failure.
  • Mitigation Planning: Helps create guardrails and mitigations based on the identified risks.
  • Use Case: Use this Skill to plan a new software development project. Imagine the project has already failed, and work backwards to identify the most likely causes.

Quick Start

Run the pre-mortem analysis for the new software project 'Great_CTO'.

Frequently Asked Questions about pre-mortem

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

FAQPage Schema
What is a pre-mortem analysis in software engineering?▼

A pre-mortem analysis identifies potential project failure causes by imagining a software project has failed and working backwards to discover risks, applying a structured 5-step process to plan mitigations.

How do I identify software project risks before development starts?▼

Run a structured 5-step pre-mortem analysis assuming project failure has already occurred, which encourages concrete risk identification and establishes guardrails to prevent those specific software engineering failures.

When should I run a pre-mortem assessment for project planning?▼

Run a pre-mortem assessment during project planning for new software development initiatives to identify threats and apply risk assessment before committing resources to the engineering phases.

Does pre-mortem analysis include mitigation planning for identified risks?▼

Yes, pre-mortem analysis includes mitigation planning by helping create guardrails and specific mitigations based on the concrete risks and causes of project failure identified during the structured assessment process.

What is the best way to analyze potential causes of project failure in software development?▼

The best way is applying a structured 5-step pre-mortem process that assumes the software project failed, working backwards to uncover concrete risks and plan appropriate mitigations for project planning.

Related Skills

Explore More Software Engineering Skills→
vp-kvp-k

Phase 0: PM Planning (순수 로직)

Automate product management planning with scoping, prioritization, and risk assessment.

Community
Advanced
cornmanwtfcornmanwtf

risk-and-assumption-tracker

Capture and manage project risks, assumptions, and mitigation plans.

Community
Intermediate
OsirsOsirs

pre-mortem

Facilitate pre-mortem analysis to identify project failures and develop mitigation strategies.

Community
Basic
fimokleifimoklei
41

pre-mortem-analyst

Simulate future project failure to identify root causes across people, process, technology, and external factors.

Community
Intermediate