Agent skill

premortem

Identify failure modes before they occur using structured risk analysis

parcadei3,879★ · 1 repos on radarProfile →
claude-coderead-onlyMIT
Install
npx skills add parcadei/Continuous-Claude-v3 --skill premortem --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 12 KB
Bundled scripts: none
Allowed tools: ReadGrepGlobTaskAskUserQuestionTodoWrite
Path: .claude/skills/premortem/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 3,885
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Pre-Mortem Identify failure modes before they occur by systematically questioning plans, designs, and implementations. Based on Gary Klein's technique, popularized by Shreyas Doshi (Stripe). ## Usage ``` /premortem # Auto-detect context, choose depth /premortem quick # Force quick analysis (plans, PRs) /premortem deep # Force deep analysis (before implementation) /premortem <file> # Analyze specific plan or code ``` ## Core Concept > "Imagine it's 3 months from now and this project has failed spectacularly. Why did it fail?" ## Risk Categories (Shreyas Framework) | Category | Symbol | Meaning | |----------|--------|---------| | **Tiger** | `[TIGER]` | Clear threat that will hurt us if not addressed | | **Paper Tiger** | `[PAPER]` | Looks threatening but probably fine | | **Elephant** | `[ELEPHANT]` | Thing nobody wants to talk about | ## CRITICAL: Verify Before Flagging **Do NOT flag risks based on pattern-matching alone.** Every potential tiger MUST go through verification. ### The False Positive Problem Common mistakes that create false tigers: - Seeing a hardcoded path without checking for `if exists():` fallback - Finding missing feature X without asking "is X in scope?" - Fl

What's inside
Steps it walks through
  1. Usage
  2. Core Concept
  3. Risk Categories (Shreyas Framework)
  4. CRITICAL: Verify Before Flagging
  5. The False Positive Problem
  6. Verification Checklist (REQUIRED)
  7. Required Evidence Format
  8. Workflow
  9. Step 1: Detect Context & Depth
  10. Step 2: Run Appropriate Checklist
  11. Step 3: Present Risks via AskUserQuestion
  12. Step 4: Handle User Response
  13. Step 5: Update Plan (if mitigations added)
  14. Integration Points
More from Continuous-Claude-v3
All skills →
About this skill
What does the premortem skill do?

Identify failure modes before they occur using structured risk analysis

How do I install it?

Run `npx skills add parcadei/Continuous-Claude-v3 --skill premortem --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 parcadei/Continuous-Claude-v3, a repository with 3,885 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.

Keep going