pre-mortem
/pre-mortem
Use before launching a plan, project, deal, or change when failure modes should be surfaced early. Use when applying the Pre Mortem consulting method and when a user asks for Pre Mortem, method execution, structured diagnosis, or action planning.
- Author
- fzfclee ↗
- Repository
- consulting-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 10.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use before launching a plan, project, deal, or change when failure modes should be surfaced early. Use when applying the Pre Mortem consulting method and when a user asks for Pre Mortem, method execution, structured diagnosis, or action planning.
Original author description
Use before launching a plan, project, deal, or change when failure modes should be surfaced early. Use when applying the Pre Mortem consulting method and when a user asks for Pre Mortem, method execution, structured diagnosis, or action planning.
How it works
- Method Notes
- Required Inputs
- When Not To Use
- Adjacent Methods
- Step-by-Step Execution
- Output Template
- Quality Gate
SKILL.md preview
--- name: pre-mortem description: Use before launching a plan, project, deal, or change when failure modes should be surfaced early. Use when applying the Pre Mortem consulting method and when a user asks for Pre Mortem, method execution, structured diagnosis, or action planning. license: Apache-2.0 --- # Pre Mortem Use this skill to run `Pre Mortem` as a practical consulting method, not as a generic framework explanation. ## Method Notes - Use prospective hindsight: assume the plan failed, then explain why. - Convert failure causes into prevention actions and early warnings. ## Required Inputs Collect or infer these inputs before execution: - planned action - success criteria - timeline - stakeholders - known risks If an input is missing, do not block automatically. Mark it as `missing`, state the assumption used, and add a validation action. ## When Not To Use Do not use after a failure has already occurred; use root-cause analysis instead. A pre-mortem requires a specific plan and time horizon, not a generic list of things that might go wrong. ## Adjacent Methods - `risk-matrix`: prioritize known risk events after they are identified. - `scenario-planning`: compare plausible external futures, not failure causes of one plan. ## Step-by-Step Execution | Step | Required input | How to execute | Output | |---|---|---|---| | Describe plan | Plan, launch date, success criteria. | State the plan as if the team believes it will work. | Plan frame. | | Assume failure | Future date and failed outcome. | Write a short future failure narrative. | Failure scenario. | | Generate causes | Team concerns, dependencies, assumptions. | List plausible reasons the plan failed. | Failure cause list. | | Prioritize preventable causes | Cause list, likelihood, impact, controllability. | Pick the causes worth preventing now. | Priority failure modes. | | Design prevention | Priority causes. | Define prevention actions, early warnings, owners, and contingencies. | Pre-mortem action plan. | ## Output Template ```markdown ### 1. Plan And Failure Horizon Plan: Launch / decision date: Assumed failure date: Success definition: ### 2. Failure Narrative The plan failed because: Observed consequences: Earliest warning: ### 3. Failure Modes | Failure mode | Cause | Preventability | Evidence | Priority | |---|---|---|---|---| | | | | | | ### 4. Prevention Plan | Prevention / contingency | Owner | Timing | Trigger | |---|---|---|---| | | | | | ### Evidence And Next Decision - Confirmed facts: - Assumptions: - Missing evidence: - Next action, owner, and timing: - Expected signal and decision threshold: ``` ## Quality Gate - Produce the method-specific outputs for Plan And Failure Horizon, Failure Narrative, Failure Modes; do not substitute a generic framework summary. - Tie every material score, causal claim, or stakeholder judgment to evidence or label it as an assumption. - Include at least one disconfirming check, sensitivity, alternative explanation, or failure condition appropriate to the method. - Convert the result into a named action or decision with an owner or stakeholder, timing, and observable signal. - State missing inputs and the smallest validation action instead of inventing precision. - Keep wording professional and plain enough that a smart non-specialist can use the output directly.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · fzfclee/consulting-skills | 100 | Apache-2.0 |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| borghei/Claude-Skills | 100 | MIT |
| ysskrishna/ai-agent-skills | 100 | MIT |
| Sidsaladi9/persona-os | 100 | MIT |
| tarunccet/pm-skills | 100 | MIT |
| kaminoikari/product-playbook | 100 | MIT |
| phuryn/pm-skills | 95 | MIT |
Database snapshot: 13.11.2026 · package version f810c2b0e172 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100aped-pre-mortem
Use when user says "pre-mortem", "what could go wrong", "risk analysis", "failure modes", "anticipate problems", or invokes aped-pre-mortem. Structured pre-mortem before implementation starts. Not for post-incident (see aped-retro). - 100risk-matrix
Use when a plan, deal, project, or stakeholder move has material downside that needs explicit controls. Use when applying the Risk Matrix consulting method and when a user asks for Risk Matrix, method execution, structured diagnosis, or action planning. - 90arn-spark-stress-premortem
This skill should be used when the user says "pre-mortem", "premortem", "risk analysis", "stress premortem", "failure analysis", "what could go wrong", "pre mortem", "investigate failure", "failure modes", or wants to stress-test a product concept by applying Gary Klein's… - 100communications-plan
Use when a decision, change, project, or stakeholder move needs coordinated communication. Use when applying the Communications Plan consulting method and when a user asks for Communications Plan, method execution, structured diagnosis, or action planning. - 100premortem
Use for pre-mortem analysis of decisions, projects, or initiatives—solo or facilitated with a team before a launch or strategic commitment. Trigger when the user says "what could go wrong", "risk assessment", "pre-mortem this", "let's run a pre-mortem", or when evaluating risks… - 100swing-mortem
Prospective failure analysis using Gary Klein's pre-mortem technique. Assumes complete failure, works backward to identify risks, leading indicators, and circuit breakers. Counters optimism bias by forcing systematic exploration of failure modes before they materialize. Use for…