premortem

premortem is a skill for Claude Code from matteotitta/genesys-skills. It costs 209 tokens per session (2,246 once invoked), scanned A, original, MIT.

A failure-planning workflow that imagines how a plan or deliverable could go wrong, then identifies safeguards. It has separate modes for strategic plans and shippable external-facing work.

In plain words
What is it for?
It reviews plans for strategic risks and checks deliverables for issues such as weak audience response, poor conversion, brand mismatch, stakeholder objections, or later deterioration.
Why use it?
It surfaces avoidable risks before work is approved or published.

Skill for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: reads .claude/ paths; names the ExitPlanMode tool.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is - **Sister skills:** [`/steal`](../../learning/steal/SKILL.md) imports patterns including this one; [`/workflow-design`](../workflow-design/SKILL.md) designs mu.

Good fit It reviews plans for strategic risks and checks deliverables for issues such as weak audience response, poor conversion, brand mismatch, stakeholder objections, or later deterioration.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/matteotitta/genesys-skills
agentmods
npx agentmods add skills/matteotitta/genesys-skills/premortem

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for premortem

README.md
[![agentmods](https://agentmods.dev/badge/skills/matteotitta/genesys-skills/premortem/github.svg)](https://agentmods.dev/skills/matteotitta/genesys-skills/premortem)
Your own site
<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/premortem"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/premortem/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for premortem

Your own site · 80×15
<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/premortem"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/premortem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 209 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,246 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00209 $0.02246
Opus 5 $0.00105 $0.01123
Sonnet 5 $0.00042 $0.00449
Haiku 4.5 $0.00021 $0.00225

Measured 11d ago against content hash 3984e4509d0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

premortem scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/meta/orchestration/premortem/SKILL.md · 171 lines

How it starts

The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/premortem — Imagine failure first, surface guardrails before commit

Two modes share one cognitive frame: write the obituary of the work, then reverse-engineer the avoidable failure. The mode flag picks the domain taxonomy.

Mode Use when Domain taxonomy Enforced how
--plan Authoring a plan file in ~/.claude/plans/ 5 strategic domains (positioning-messaging / channel-distribution / stakeholder-alignment / execution-velocity / market-regulatory) BLOCK via .claude/hooks/exit-plan-premortem-check.sh at ExitPlanMode
--output Producing a client-facing or external-facing deliverable (LinkedIn post, AEO article, landing-page-copy, proposal, positioning lock, messaging library, etc.) 5 execution domains (will-it-resonate / will-it-convert / will-it-stay-on-brand / will-stakeholder-push-back / will-it-degrade-over-time) SOFT-WARN via _schema/validate-frontmatter.py check_output_premortem_contract()

If invoked without a flag, ask the user which mode applies. Don't generate a generic premortem — the value is in the mode-specific domains.


When to use --plan

You're writing a plan file (most often in ~/.claude/plans/ during plan mode, or a delivery plan in docs/). The Auto-Challenge Protocol "For Plans" check + the planning-doctrine pre-ExitPlanMode 8-gate already cover completeness and clarity. Premortem covers what those miss: strategic blind spots the author can't see because they just convinced themselves the approach works.

The hook enforces presence: ExitPlanMode will exit non-zero with Plan missing required ## Premortem section if you skip it.

When to use --output

You're producing a shippable deliverable. The output is going in front of a client, a prospect, an external audience, or a public surface. Examples:

  • LinkedIn post, AEO article, newsletter issue
  • Landing page copy, sales deck, proposal
  • Positioning lock, messaging library, ICP synthesis ready for client review
  • Pricing strategy doc, content strategy doc

Read the full file on GitHub · 171 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 171 lines · 209 tokens per session scan A 3984e4509d0b

Subscribe to this mod's changes

premortem is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 209 tokens to every session and 2,246 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

gingiris-b2b-growth

🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…

Gingiris-1031/gingiris-skills · 484 tokens

gr-b2b-growth

A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.

Gingiris-1031/gingiris-skills · 83 tokens

go-to-market-playbook

A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.

Gingiris-1031/gingiris-skills · 48 tokens

gingiris-go-global

🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles.…

Gingiris-1031/gingiris-skills · 534 tokens

gr-competitor-research

Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…

Gingiris-1031/gingiris-skills · 582 tokens

ai-launch-playbook

Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.

Gingiris-1031/gingiris-skills · 54 tokens