pre-mortem

Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable pre-mortem skill with a clear sequenced workflow and concrete risk taxonomy plus output template. The only real slack is mild over-explanation in the Context section and the absence of validation checkpoints (which are not strictly required for an analysis-only task).

Suggestions

Tighten or remove the Context paragraph's definition of what a pre-mortem is—Claude already knows this—keeping only any non-obvious framing.

Add a brief validation/verification checkpoint after categorization (e.g., re-scan for any unclassified risks before writing Action Plans) to push workflow clarity higher.

If the risk taxonomy or output template grows, move them into a referenced file to make progressive-disclosure structure explicit.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with well-organized actionable instructions, though the Context paragraph ("A pre-mortem is a structured risk-identification exercise that forces teams to think critically...") explains a concept Claude already knows and could be trimmed.	4 / 5
Actionability	Provides concrete, specific guidance throughout: explicit definitions and criteria for Tigers/Paper Tigers/Elephants, urgency tiers with examples, action-plan fields (Risk, Mitigation, Owner, Due Date), and a copy-ready output template covering the common cases.	5 / 5
Workflow Clarity	A clear seven-step sequence runs from gathering the PRD through saving output, but there are no explicit validation/checkpoint steps; this is acceptable for an analysis task yet keeps it just below the top anchor.	4 / 5
Progressive Disclosure	Content is well-sectioned (Purpose, Context, Instructions, Notes, Further Reading) with external reading links cleanly placed at the end and no nested references, though there is no file-split structure to demonstrate one-level-deep navigation.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete actions, comprehensive natural trigger terms, and an explicit Use-when clause tied to a distinctive methodology. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—"Run a pre-mortem risk analysis", "Categorizes risks as Tigers...Paper Tigers...Elephants", and "classifies as launch-blocking, fast-follow, or track"—giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what (run pre-mortem, categorize and classify risks) and when ("Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms a user would say are well covered: "pre-mortem", "risk analysis", "PRD", "launch plan", "preparing for launch", "stress-testing a product plan", "identifying what could go wrong".	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche—pre-mortem risk analysis with its own Tigers/Paper Tigers/Elephants vocabulary—so its triggers are distinct and conflict risk with other skills is minimal.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: phuryn/pm-skills
Path: pm-execution/skills/pre-mortem/SKILL.md
Commit: 18468a9

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.