Individual skill

s4h-historical-failure-analysis

Extracts recurring failure modes from similar past situations — most failures have happened before in recognisable patterns. TRIGGERS: 'what usually goes wrong', 'failure pattern analysis', 'how do these typically fail', 'what went wrong last time', 'avoid past mistakes'.

skills/s4h-historical-failure-analysis/SKILL.md

Read pinned source

Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 241
Repository last updated: Jul 15, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
claude-code-plugin Repository topic
cognitive-frameworks Repository topic
creativity Repository topic
decision-making Repository topic
ethics Repository topic
mental-models Repository topic
problem-solving Repository topic
reasoning Repository topic
systems-thinking Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 6,481 bytes

Read excerpt


# Historical Failure Analysis

Post-mortems reveal the same failure modes repeating across organisations, industries,
and eras. Execution failure at handoff. Stakeholder misalignment discovered too late.
Scope expansion under pressure that destroys the original design. Underestimated
dependencies that required other things to change first. The failure modes aren't a
mystery — they just don't get applied prospectively. This skill does that: surfaces
which patterns are present now, before they become post-mortem findings.

---

## Your Process

**Step 1: Describe the Type of Endeavour**