Pre Mortem
Imagine the project has already shipped and failed catastrophically — work backwards from the failure to identify the most likely causes BEFORE building. Forces concrete risk identification, not vague "what could go wrong" lists.
Install
npx skills add jeremybrasher/grokbot-skills --skill pre-mortemgit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/pre-mortem ~/.claude/skills/pre-mortemPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Pre-mortem — fail-it-before-you-build-it A retrospective for a project that hasn't happened yet. Surfaces real risks that "list every risk" prompts miss. Originated in Gary Klein's research at MIT Sloan, now standard at AWS and other ops-mature orgs. ## The 5-step pre-mortem ### Step 1. Imagine you're 6 months in the future The project shipped. It is a clear, public failure. There's a Reddit thread about it. The CEO is asking what went wrong. ### Step 2. Write the post-mortem newspaper headline One sentence. Concrete. Specific. Examples: - ❌ Bad: "We had some quality issues." - ✅ Good: "On 2026-09-12, the Stripe webhook handler deduplicated by raw body hash, so 30K customers were double-charged after Stripe retried delivery during a network blip." The headline forces you to name the failure mode SPECIFICALLY. ### Step 3. List every individual reason this exact failure happened Brainstorm 10-15 reasons. Be specific. Each item should reference: - A real component / file - A real failure mode (race condition, schema mismatch, expired credential) - A real human factor (oncall didn't see alert, runbook was outdated) Reject hand-waves like "testing was insufficient." Replace with "we didn't write a property-based test for the dedup-key collision case." ### Step 4. Rank by likelihood × severity For each cause, score: - **Likelihood:** 1-5 (1=once-in-a-decade, 5=monthly) - **Severity:** 1-5 (1=cosmetic, 5=data loss / regulatory breach)
Details
- Skill name
pre-mortem- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/pre-mortem/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Pre Mortem skill do?
Imagine the project has already shipped and failed catastrophically — work backwards from the failure to identify the most likely causes BEFORE building. Forces concrete risk identification, not vague "what could go wrong" lists.
How do I install the Pre Mortem skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill pre-mortem. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Pre Mortem popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Systematic Debugging
38jeremybrasher/grokbot-skills
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Observe the failure first. Do not use it to implement an already-approved design, to add a feature with no failing behavior, or to guess a root cause from a one-line complaint.
Discovery
38jeremybrasher/grokbot-skills
Structured pre-design questioning to surface hidden constraints before any architecture decision is locked in. Forces the architect/auditor/reviewer to enumerate what they DON'T know before proposing.
Test Driven Development
38jeremybrasher/grokbot-skills
Use when implementing any feature or bugfix, before writing implementation code. Observe the required behavior first. Do not use it to keep a green suite that encodes the wrong object, to write tests after the code, or to ship production code without a failing test.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.