Run any Skill in Manus with one click

pre-mortem-analyst

Stars39

Forks8

UpdatedFebruary 8, 2026 at 22:34

Imagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain. Use when user says "pre-mortem", "premortem", "imagine this failed", "what could go wrong", "risk analysis", "before we launch", "stress test", "what would kill this", "project risks".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

fimoklei

fimoklei/pm-ai-playbook

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

General and Operations ManagersManagement Occupations·SOC 11-1021

File Explorer

4 files

SKILL.md

readonly

name	pre-mortem-analyst
description	Imagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain. Use when user says "pre-mortem", "premortem", "imagine this failed", "what could go wrong", "risk analysis", "before we launch", "stress test", "what would kill this", "project risks".

Pre-Mortem Analyst

Why Pre-Mortem > Risk Assessment

Risk Assessment: "What MIGHT go wrong?" → Optimism bias filters answers Pre-Mortem: "It's 6 months later. It's FAILED. Why?" → Liberates honest analysis

Research: Pre-mortems increase problem identification by 30%.

The Process

Set the scene: "It's [date]. This has failed completely."
Brainstorm causes: List 10+ failure reasons (no filtering)
Categorize: People, Process, Technology, External
Rate: Likelihood × Impact (H/M/L)
Prevent: Top 3 get specific mitigation actions
Monitor: Define early warning signs

Output Format

PROJECT: [Name]
FAILURE SCENARIO: "It's [date]. [Project] has completely failed."

WHY IT FAILED:

👥 PEOPLE: [Cause] - L×I: H/H | Prevent: [x] | Warning: [y]
⚙️ PROCESS: [Cause] - L×I: M/H | Prevent: [x] | Warning: [y]
💻 TECHNOLOGY: [Cause] - L×I: L/H | Prevent: [x] | Warning: [y]
🌍 EXTERNAL: [Cause] - L×I: M/M | Prevent: [x] | Warning: [y]

TOP 3 PRIORITIES:
1. [Risk] → [Specific action]
2. [Risk] → [Specific action]
3. [Risk] → [Specific action]

WARNING SIGNS TO MONITOR:
□ [Early indicator 1]
□ [Early indicator 2]

Common Failure Categories

Category	Common Causes
People	Key person leaves, skill gaps, misalignment, low buy-in
Process	Aggressive timeline, scope creep, dependency issues
Tech	Doesn't scale, integration fails, security breach
External	Market shift, competitor move, regulation change

Integration

Compounds with:

inversion-strategist → Create systematic avoidance strategies
second-order-consequences → Project impact of prevented failures
first-principles-decomposer → Question hidden assumptions
mspot-generator → Validate MSPOT projects before committing

See references/examples.md for Artem-specific pre-mortems

More from this repository

same repository

intent-layer

fimoklei/pm-ai-playbook

Use when initializing or maintaining agent-friendly repo context, setting up AGENTS.md or CLAUDE.md, adding local rules, defining verification commands, or checking whether context files are stale.

2026-05-3139

workflow-ship

fimoklei/pm-ai-playbook

Use when the user asks to run workflow:ship, ship a branch, publish a feature branch, open and merge a PR, or push/PR/merge/cleanup completed work.

2026-05-1739

workflow-commit

fimoklei/pm-ai-playbook

Use when the user asks to run workflow:commit, create a commit, make a git commit, stage changes, write a commit message, or prepare local changes for shipping.

2026-05-1739

fimoklei/pm-ai-playbook

Turn any rough prompt, half-formed idea, or task description into a finished, ready-to-send prompt optimized for Opus 4.7 (with adaptive thinking) inside the chat app — claude.ai, the Mac app, the iOS app — NOT the API. Use this skill whenever the user wants to write, rewrite, optimize, improve, sharpen, or polish a prompt for the chat app. Trigger phrases include "rewrite this prompt", "make this a better prompt", "optimize this prompt", "turn this into a prompt", "help me prompt this", "draft a prompt that...", "I want to ask...", or whenever the user pastes a draft prompt and asks for improvements. Also trigger when the user describes a task they plan to send into the chat app and clearly wants a reusable, well-structured prompt rather than a direct answer. The output is always a single, copy-pasteable prompt in a code block that the user sends as-is — never a template with placeholders. Always ends with the exact line "Think before answering (maximum reasoning)".

2026-05-1039

kiro-discovery

fimoklei/pm-ai-playbook

Entry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.

2026-05-0839

kiro-intent

fimoklei/pm-ai-playbook

Pre-discovery intent exploration for genuinely vague ideas. Use when the user pitches an idea where the real user-need, problem framing, or core assumptions are unclear — before /kiro-discovery. Delegates to the intent-explorer skill, which produces .kiro/specs/<slug>/intent-spec.md. The output is auto-detected by /kiro-discovery and downstream spec skills, so the user does not need to pass intent context as an argument. Skip this skill entirely when the user already has a clear problem statement.

2026-05-0839

name	pre-mortem-analyst
description	Imagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain. Use when user says "pre-mortem", "premortem", "imagine this failed", "what could go wrong", "risk analysis", "before we launch", "stress test", "what would kill this", "project risks".

Pre-Mortem Analyst

Why Pre-Mortem > Risk Assessment

Risk Assessment: "What MIGHT go wrong?" → Optimism bias filters answers Pre-Mortem: "It's 6 months later. It's FAILED. Why?" → Liberates honest analysis

Research: Pre-mortems increase problem identification by 30%.

The Process

Set the scene: "It's [date]. This has failed completely."
Brainstorm causes: List 10+ failure reasons (no filtering)
Categorize: People, Process, Technology, External
Rate: Likelihood × Impact (H/M/L)
Prevent: Top 3 get specific mitigation actions
Monitor: Define early warning signs

Output Format

PROJECT: [Name]
FAILURE SCENARIO: "It's [date]. [Project] has completely failed."

WHY IT FAILED:

👥 PEOPLE: [Cause] - L×I: H/H | Prevent: [x] | Warning: [y]
⚙️ PROCESS: [Cause] - L×I: M/H | Prevent: [x] | Warning: [y]
💻 TECHNOLOGY: [Cause] - L×I: L/H | Prevent: [x] | Warning: [y]
🌍 EXTERNAL: [Cause] - L×I: M/M | Prevent: [x] | Warning: [y]

TOP 3 PRIORITIES:
1. [Risk] → [Specific action]
2. [Risk] → [Specific action]
3. [Risk] → [Specific action]

WARNING SIGNS TO MONITOR:
□ [Early indicator 1]
□ [Early indicator 2]

Common Failure Categories

Category	Common Causes
People	Key person leaves, skill gaps, misalignment, low buy-in
Process	Aggressive timeline, scope creep, dependency issues
Tech	Doesn't scale, integration fails, security breach
External	Market shift, competitor move, regulation change

Integration

Compounds with:

inversion-strategist → Create systematic avoidance strategies
second-order-consequences → Project impact of prevented failures
first-principles-decomposer → Question hidden assumptions
mspot-generator → Validate MSPOT projects before committing

See references/examples.md for Artem-specific pre-mortems