Premortem
Run a premortem on any plan, launch, product, hire, strategy, or decision. Imagines it failed 6 months from now, works backward to find every reason why, then produces a revised plan. Triggers include "premortem this", "premortem my", "what could kill this", "stress test this plan", "find the blind spots", "poke holes in this", "where will this break", "am I missing anything", "what could go wrong", "future-proof this", "devil's advocate this".
Install
npx skills add b1rdmania/claude-premortem-skill --skill premortemgit clone --depth 1 https://github.com/b1rdmania/claude-premortem-skill.git /tmp/claude-premortem-skill
mkdir -p ~/.claude/skills
cp -r /tmp/claude-premortem-skill/. ~/.claude/skills/premortemPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Premortem The opposite of a postmortem. Imagine the plan already failed and work backward to find why, before you start. - Method: Gary Klein, *Harvard Business Review*, 2007. - Kahneman praised it in *Thinking, Fast and Slow* as a way to counter overconfidence. - Widely adopted in corporate strategy and project planning. - Mechanism: "what could go wrong?" produces hedged, polite answers. "This already failed, explain why" puts the brain into narrative mode and generates specific, honest causes. Wharton/Cornell call this "prospective hindsight." Why it matters for AI assistance: Claude defaults to agreeable. Asking "is this a good plan?" gets reasons it's good. The premortem reframe forces honest failure analysis instead of polite risk assessment. ## When NOT to apply - Vague ideas with no concrete plan yet (help plan first, then premortem) - Questions with one right answer (just answer) - Creative feedback on a draft (that's editing) - Decisions already made and irreversible (premortem only helps when course correction is possible) - Requests for multi-perspective decision support (use LLM Council instead — different mechanism, different output) - Simple feedback or factual questions ## Step 1 — Gather minimum context A premortem is only as good as its input. You need three things: 1. **What is it?** — describe the plan in one sentence 2. **Who is it for?** — audience, customer, team, stakeholders 3. **What does success look like?** — failure is the inverse
Details
- Skill name
premortem- Repository
- b1rdmania/claude-premortem-skill
- License
- MIT
- Repo updated
- 29 August 2026
FAQ
What does the Premortem skill do?
Run a premortem on any plan, launch, product, hire, strategy, or decision. Imagines it failed 6 months from now, works backward to find every reason why, then produces a revised plan. Triggers include "premortem this", "premortem my", "what could kill this", "stress test this plan", "find the blind spots", "poke holes in this", "where will this break", "am I missing anything", "what could go wrong", "future-proof this", "devil's advocate this".
How do I install the Premortem skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add b1rdmania/claude-premortem-skill --skill premortem. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Premortem popular?
It lives in b1rdmania/claude-premortem-skill, which has 30 GitHub stars and 2 forks.
Related skills
Molt Dex
23ReSo7200/molt-dex
Reverse-engineer and assess Android apps, from unobfuscated to heavily obfuscated, using a staged, evidence-first pipeline built on apktool, adb and scrcpy. Use when the user wants to understand how an APK is built, what it does, where its secrets and misconfigurations are, or wants to drive an app on a device to observe its behaviour. Dynamic testing (anything that touches a running system or backend) is authorization-gated and must be in scope.
Vibe Testing
24knot0-com/vibe-testing
This skill should be used when the user asks to "test my specs", "validate my design docs", "find gaps in my architecture", "stress-test the spec", "vibe test", "pressure test the docs", or mentions spec validation before implementation begins.
Sketch Narrator
22qingyabailu-git/SketchNarrator
从中文主题、文案、视频链接、本地音视频或参考角色制作带自然配音、真实音频时间、分区笔迹和内部成片 QA 的完整手绘讲解视频。适用于素材转口播、黑板讲解、白板科普、故事口播和系列 IP 手绘视频;不用于纯 AI 视频模型生成或复杂 Web 工作台建设。
Trip Planner
47skywain/trip-planner-skill
End-to-end international trip planning: turns "I want to go to X for N days" into a verified, bookable plan — route skeleton across cities, flight price scans (international + domestic legs), train-vs-fly decisions, hour-by-hour daily timelines with opening hours, dwell times, holiday collisions and tappable turn-by-turn map links (小时级行程+地图导航+离线KML), hotel shortlists by neighborhood, budget rollup, and a booking checklist with deep links. Use this whenever the user asks to plan a trip, vacation, itinerary or honeymoon, compare flight dates/prices, pick between cities or routes, schedule a trav
Zod
24anivar/zod-skill
Zod v4 best practices, patterns, and API guidance for schema validation, parsing, error handling, and type inference in TypeScript applications. Covers safeParse, object composition, refinements, transforms, codecs, branded types, v3→v4 migration, and testing schemas with Jest or Vitest. Baseline: zod ^4.6.0. Triggers on: zod imports, z.object, z.string, z.infer, safeParse, mentions of "zod", "schema validation", "zod v4", "z.enum", or testing a schema — "schema test", "zod mock", zod-schema-faker.
Econometrics
41xiaomihu1992/econometrics-skill
Causal inference and applied econometric analysis on tabular data, from uploaded-data diagnostics and cleaning advice to treatment-effect estimation and publication-grade applied research design. Use for policy impact, ATE/ATT/LATE/ITT, OLS, propensity scores, IV/2SLS, DID/event studies, RDD, robustness checks, falsification tests, identification memos, 因果推断, 政策评估, 数据清洗建议, 稳健性检验, and 异质性分析.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.