openclaw 网盘下载
OpenClaw

技能详情(站内镜像,无评论)

首页 > 技能库 > Pre-Mortem Analyst

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", "stres…

开发与 DevOps

许可证:MIT-0

MIT-0 ·免费使用、修改和重新分发。无需归因。

版本:v1.0.0

统计:⭐ 4 · 2.8k · 14 current installs · 14 all-time installs

4

安装量(当前) 14

🛡 VirusTotal :良性 · OpenClaw :良性

Package:artyomx33/pre-mortem-analyst

安全扫描(ClawHub)

  • VirusTotal :良性
  • OpenClaw :良性

OpenClaw 评估

This is an instruction-only pre-mortem facilitation skill whose required artifacts and runtime instructions are consistent with its description and do not request credentials, installs, or system access.

目的

The name/description (pre-mortem analysis) matches the contents: facilitation steps, templates, examples, and frameworks for imagining failure. There are no unrelated requirements (no env vars, binaries, or installs) that would be unexpected for this purpose.

说明范围

SKILL.md and reference docs provide step-by-step facilitation guidance, output templates, examples, and monitoring suggestions. The instructions do not tell the agent to read files, access environment variables, contact external endpoints, or collect system data beyond the user-provided project context.

安装机制

No install spec or code files that would be written to disk or executed are present. Being instruction-only minimizes supply-chain/code-execution risk.

证书

The skill requests no environment variables, credentials, or config paths. This is proportionate for a facilitation/analysis skill that only needs user-provided project context.

持久

always is false and default autonomous invocation is unchanged. The skill does not request persistent presence, system modification, or access to other skills' config.

综合结论

This skill is instruction-only and internally consistent with being a pre-mortem facilitator. It does not request credentials or install code, so supply-chain and credential-exfiltration risks are low. However, be cautious about the project data you paste into any third-party model or agent — do not include secrets, credentials, or sensitive PII in prompts. If you plan to run pre-mortems on proprietary projects, confirm how your agent/provider…

安装(复制给龙虾 AI)

将下方整段复制到龙虾中文库对话中,由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库(龙虾 AI)执行:为本机安装 OpenClaw 技能「Pre-Mortem Analyst」。简介:Imagine the project already failed, then work backward to find why. More powerf…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装:https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/artyomx33/pre-mortem-analyst/SKILL.md
(来源:yingzhi8.cn 技能库)

SKILL.md

打开原始 SKILL.md(GitHub raw)

---
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 FAILED. Why?" → Liberates honest analysis

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

## The Process

1. **Set the scene:** "It's [date]. This has failed completely."
2. **Brainstorm causes:** List 10+ failure reasons (no filtering)
3. **Categorize:** People, Process, Technology, External
4. **Rate:** Likelihood × Impact (H/M/L)
5. **Prevent:** Top 3 get specific mitigation actions
6. **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