historical-failure-analysis

Match current initiatives to historical post-mortem failure patterns and rank risks.

212|23|Updated May 23, 2026
One-click install
npx skills add https://github.com/human-avatar/skills-for-humanity --skill historical-failure-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: historical-failure-analysis
Source: https://github.com/human-avatar/skills-for-humanity/tree/main/skills/historical-failure-analysis
Command: npx skills add https://github.com/human-avatar/skills-for-humanity --skill historical-failure-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Historical failure analysis helps you identify which recurring failure modes are most likely to derail your current initiative before they become post-mortem conclusions.

Core Features & Use Cases

  • Failure mode extraction: Maps your endeavour to common patterns such as underestimated dependencies, late stakeholder misalignment, scope expansion under pressure, handoff/ownership breakdowns, context assumption failure, resource attrition, and missing feedback loops.
  • Evidence-based testing: Converts each failure mode into concrete early warning signs and checks whether they are already present or emerging in your current situation.
  • Risk prioritization: Ranks top risks using probability × impact (H/M/L) so you focus on the few most fatal threats.
  • Pre-emptive action planning: Defines specific actions to take now for the top three failure modes, including timing and ownership.

Quick Start

Use the historical-failure-analysis skill to assess your initiative by running a failure-mode table against its current conditions and producing pre-emptive actions for the top three likely failures.

Frequently Asked Questions about historical-failure-analysis

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

FAQPage Schema
What is failure analysis and how does it prevent execution risk in product launches?▼

Failure analysis identifies recurring failure modes by matching your initiative to historical post-mortem patterns. It prevents execution risk by converting patterns like underestimated dependencies and stakeholder misalignment into early warning signs you can test for now.

How do I conduct a post-mortem analysis before a project actually fails?▼

To conduct a pre-emptive post-mortem analysis, map your initiative to historically observed failure modes, check for early warning signs of those patterns, rank risks by probability and impact, and define pre-emptive actions for the top three threats.

Can I use historical failure patterns for organizational transformations and scaling efforts?▼

Yes, historical failure pattern matching applies to organizational transformations, technology implementations, negotiations, and scaling efforts. It evaluates execution risks like ownership handoffs and missing feedback loops that emerge over time in these contexts.

What is the best way to prioritize execution risks and dependency planning failures?▼

The best way to prioritize execution risks is ranking them using probability multiplied by impact. This focuses your dependency planning on the few most fatal threats and triggers specific pre-emptive actions with defined timing and ownership.

Why does stakeholder misalignment happen during technology implementations and how is it detected?▼

Stakeholder misalignment happens when context assumptions fail during execution. It is detected by mapping your technology implementation to historical failure modes and testing for concrete early warning signs of misalignment already present in your situation.

When should I not rely on historical failure analysis for risk prioritization?▼

You should not rely on historical failure analysis when your initiative faces entirely novel conditions lacking historically observed post-mortem patterns, or when execution risks cannot be measured by probability and impact ranking.