Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
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".
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".
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Risk Assessment: "What MIGHT go wrong?" β Optimism bias filters answers Pre-Mortem: "It's 6 months later. It FAILED. Why?" β Liberates honest analysis Research: Pre-mortems increase problem identification by 30%.
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
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]
CategoryCommon CausesPeopleKey person leaves, skill gaps, misalignment, low buy-inProcessAggressive timeline, scope creep, dependency issuesTechDoesn't scale, integration fails, security breachExternalMarket shift, competitor move, regulation change
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
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.