premortem
Identify failure modes before they occur. Use when reviewing plans, designs, or PRs to catch risks early. Not for post-incident analysis or debugging active issues.
Profile →npx skills add majiayu000/claude-skill-registry --skill premortem-git-fg-meta-plugin-manager --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Pre-Mortem <mission_control> <objective>Identify failure modes before they occur by systematically questioning plans, designs, and implementations with verified evidence requirements</objective> <success_criteria>Risks categorized (Tiger/Paper/Elephant) with specific verification evidence, HIGH severity risks addressed before proceeding</success_criteria> </mission_control> <trigger>When reviewing plans, designs, or PRs to catch risks early. Not for: Post-incident analysis or debugging active issues.</trigger> <interaction_schema> DETECT_CONTEXT → RUN_CHECKLIST → VERIFY_FINDINGS → PRESENT_RISKS → UPDATE_PLAN </interaction_schema> Identify failure modes before they occur by systematically questioning plans, designs, and implementations. Based on Gary Klein's technique, popularized by Shreyas Doshi (Stripe). ## Core Concept > "Imagine it's 3 months from now and this project has failed spectacularly. Why did it fail?" ## Risk Categories | Category | Symbol | Meaning | | --------------- | ------------ | ----------------------------------------------- | | **Tiger** | `[TIGER]` | Clear threat that will hurt us if not addressed | | **Paper Tiger** | `[PAPER]` | Looks threatening but pro
- Core Concept
- Risk Categories
- CRITICAL: Verify Before Flagging
- The False Positive Problem
- Verification Checklist (REQUIRED)
- Required Evidence Format
- Workflow
- Step 1: Detect Context & Depth
- Step 2: Run Appropriate Checklist
- Step 3: Present Risks via AskUserQuestion
- Step 4: Handle User Response
- Step 5: Update Plan (if mitigations added)
- Severity Thresholds
- Example Session
What does the premortem skill do?
Identify failure modes before they occur. Use when reviewing plans, designs, or PRs to catch risks early. Not for post-incident analysis or debugging active issues.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill premortem-git-fg-meta-plugin-manager --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.