Prd V09 Hn Reddit Launch
mattgierhart/PRD-driven-context-engineering
Build a Hacker News + Reddit launch playbook for developer-tools and community-led products during PRD v0.9 Go-to-Market.
Run a pre-mortem risk analysis on a PRD or launch plan. An agent skill from phuryn/pm-skills.
Install Pre Mortem
$ npx skills add phuryn/pm-skills --skill pre-mortem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install phuryn/pm-skills pre-mortem --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pm-execution/skills/pre-mortem .claude/skills/pre-mortem && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pre-mortem" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/pre-mortem into .claude/skills/pre-mortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-mortem", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/pre-mortemType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add phuryn/pm-skills --skill pre-mortem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install phuryn/pm-skills pre-mortem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pm-execution/skills/pre-mortem .agents/skills/pre-mortem && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pre-mortem" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/pre-mortem into .agents/skills/pre-mortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-mortem", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add phuryn/pm-skills --skill pre-mortem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install phuryn/pm-skills pre-mortem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pm-execution/skills/pre-mortem .cursor/skills/pre-mortem && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pre-mortem" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/pre-mortem into .cursor/skills/pre-mortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-mortem", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/phuryn/pm-skills.git --path pm-execution/skills/pre-mortem--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add phuryn/pm-skills --skill pre-mortem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install phuryn/pm-skills pre-mortem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pm-execution/skills/pre-mortem .gemini/skills/pre-mortem && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pre-mortem" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/pre-mortem into .gemini/skills/pre-mortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-mortem", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install phuryn/pm-skills pre-mortemInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add phuryn/pm-skills --skill pre-mortem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/pm-execution/skills/pre-mortem .github/skills/pre-mortem && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pre-mortem" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/pre-mortem into .github/skills/pre-mortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-mortem", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add phuryn/pm-skills --skill pre-mortem -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install phuryn/pm-skills pre-mortem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pm-execution/skills/pre-mortem .opencode/skills/pre-mortem && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pre-mortem" agent skill from https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/pre-mortem into .opencode/skills/pre-mortem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-mortem", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pre-mortem- GitHub stars
- 27k
- Token cost
- ~1k tokens
- SKILL.md length
- 426 words
- Files
- 1
- Skills in repo
- 62
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run a pre-mortem risk analysis on a PRD or launch plan. An agent skill from phuryn/pm-skills.
- Works in 7 steps: Gather the PRD: If the user provides a… → Think Step by Step → Categorize Risks: Classify each… → …
- Preparing for launch
- SKILL.md covers Purpose, Context, Instructions and Notes
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pre Mortem is an agent skill from phuryn/pm-skills. 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.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Product launch strategy, PRD writing and Load testing. The repository describes itself as: PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth. The licence is MIT.
When your agent uses it
- Preparing for launch
- Stress-testing a product plan
- Identifying what could go wrong
Example prompts
- “/pre-mortem”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Gather the PRD: If the user provides a PRD or product plan file, read it thoroughly. Understand the product, target market, key…
- Think Step by Step
- Categorize Risks: Classify each potential failure as one of three types
- Classify Tigers by Urgency
- Create Action Plans: For every Launch-Blocking Tiger
- Structure Output: Present the analysis as
- Save the Output: Save as a markdown document: PreMortem-[product-name]-[date].md
What it can do on your machine
Read from SKILL.md and the folder at commit 8607e3b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
productcompass.pm
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pre Mortem loads about 1k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 426 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from phuryn/pm-skills at commit 8607e3b, republished under its MIT licence (© phuryn). 426 words, ~1,020 tokens.
Download SKILL.mdSave it as
.claude/skills/pre-mortem/SKILL.md (or your agent's skills folder).- name
- pre-mortem
- description
- 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.
Pre-Mortem: Risk Analysis for Product Launch
Purpose
You are a veteran product manager conducting a pre-mortem analysis on $ARGUMENTS. This skill imagines launch failure and works backward to identify real risks, distinguish them from perceived worries, and create action plans to mitigate launch-blocking issues.
Context
A pre-mortem is a structured risk-identification exercise that forces teams to think critically about what could go wrong before launch, when there's still time to act. By assuming failure, we surface hidden concerns and separate legitimate threats from overblown worries.
Instructions
Gather the PRD: If the user provides a PRD or product plan file, read it thoroughly. Understand the product, target market, key assumptions, and timeline. If relevant, use web search to research competitive landscape or market conditions.
Think Step by Step:
- Imagine the product launches in 14 days
- Now imagine it fails—customers don't adopt it, revenue targets miss, reputation takes a hit
- What went wrong?
- What did we miss or not execute well?
- What were we overconfident about?
Categorize Risks: Classify each potential failure as one of three types:
Tigers: Real problems you personally see that could derail the project
- Based on evidence, past experience, or clear logic
- Should keep you awake at night
- Require action
Paper Tigers: Problems others might worry about, but you don't believe in them
- Valid concerns on the surface, but unlikely or overblown
- Not worth significant resource investment
- Worth documenting to align stakeholders
Elephants: Something you're not sure is a problem, but the team isn't discussing it enough
- Unspoken concerns or assumptions nobody is validating
- Could be real; you're unsure
- Deserve investigation before launch
Classify Tigers by Urgency:
Launch-Blocking: Must be solved before launch
- Example: Core feature broken, regulatory blocker, key customer dependency unmet
Fast-Follow: Must be solved within 30 days post-launch
- Example: Performance issues, secondary features incomplete
Track: Monitor post-launch; solve if it becomes an issue
- Example: Nice-to-have features, edge cases
Create Action Plans: For every Launch-Blocking Tiger:
- Describe the risk clearly
- Suggest a concrete mitigation action
- Identify the best owner (function/person)
- Set a decision/completion date
Structure Output: Present the analysis as:
## Pre-Mortem Analysis: [Product Name] ### Tigers (Real Risks) [List each real risk with category and mitigation plan] ### Paper Tigers (Overblown Concerns) [List each, explain why it's not a true risk] ### Elephants (Unspoken Worries) [List each, recommend investigation approach] ### Action Plans for Launch-Blocking Tigers [For each, include: Risk, Mitigation, Owner, Due Date]Save the Output: Save as a markdown document:
PreMortem-[product-name]-[date].md
Show full SKILL.md (66 more words)Show less
Notes
- Be honest and constructive—the goal is to improve launch readiness, not assign blame
- Default to "Tiger" if unsure; it's better to address risks early
- Involve cross-functional perspectives (engineering, design, go-to-market) in your analysis
- Revisit the pre-mortem 2-3 weeks before launch to verify mitigations are on track
Further Reading
© phuryn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in pm-execution/skills/pre-mortem of phuryn/pm-skills.
Open the folder on GitHubat commit 8607e3b
Compare with similar skills
Pre Mortem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pre Mortem this skillphuryn/pm-skills | 27k | — | ~1k | Automated safety check: Pass | MIT | |
| Prd V09 Hn Reddit Launchmattgierhart/PRD-driven-context-engineering | 179 | — | ~2.8k | Automated safety check: Pass | MIT | |
| First 1000 UsersLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.1k | Automated safety check: Pass | MIT | |
| PlaidBuildGreatProducts/plaid | 217 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Rfc Modelingmirumee/nimara-ecommerce | 129 | — | ~920 | Automated safety check: Pass | BSD-3-Clause | |
| Enrichmenteser/stack | 128 | — | ~642 | Automated safety check: Pass | Custom licence |
Similar skills
First 1000 Users
LeoYeAI/openclaw-master-skills
AI-powered Reddit seeding agent for founders. An agent skill from LeoYeAI/openclaw-master-skills.
Plaid
BuildGreatProducts/plaid
Product Led AI Development — guides founders from idea to launched product.
Rfc Modeling
mirumee/nimara-ecommerce
A skill your agent uses when designing, drafting, refining, or stress-testing an RFC for an approved PRD, including requests for a design doc, solution design, or how to build it.
Enrichment
eser/stack
Interviews the user about a plan, decision or idea in rounds, level by level down a decision tree, until both share one understanding; facts are researched by sub-agents, decisions stay with the user.
Grilling Ideas
opsmill/infrahub
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written.
More from phuryn/pm-skills
All 62 skills in this repoAgreement-Based Code Review
phuryn/pm-skills
Reviews a diff by anchoring on agreements between two sides of a boundary, forcing a concrete violating execution, and refuting each finding before reporting it.
A/B Test Analysis
phuryn/pm-skills
Validates an experiment's setup, works out lift, p-value and confidence interval from A/B test data, and recommends whether to ship, extend or stop.
Team OKR Brainstorm
phuryn/pm-skills
Drafts three alternative sets of team OKRs, each with an inspiring objective and measurable key results, tied to the company strategy you provide.
Cohort Analysis and Retention Explorer
phuryn/pm-skills
Analyzes uploaded cohort data to compute retention curves and feature adoption trends, builds heatmaps and charts, and suggests qualitative follow-up research.
Dummy Dataset Generator
phuryn/pm-skills
Generates realistic test datasets with custom columns, row counts and business constraints, output as CSV, JSON, SQL inserts or a runnable Python script.
Grammar and Flow Checker
phuryn/pm-skills
Reviews a draft for grammar, logic and flow problems and returns located, prioritized fix suggestions without rewriting the whole text.
Related
Questions about Pre Mortem
What does Pre Mortem do?
Run a pre-mortem risk analysis on a PRD or launch plan. An agent skill from phuryn/pm-skills. Pre Mortem is an agent skill from phuryn/pm-skills. Run a pre-mortem risk analysis on a PRD or launch plan.
When should I use Pre Mortem?
Pre Mortem fits situations like: preparing for launch; stress-testing a product plan; identifying what could go wrong.
How do I install Pre Mortem in Claude Code?
Run `npx skills add phuryn/pm-skills --skill pre-mortem -a claude-code`. Or copy the skill folder (pm-execution/skills/pre-mortem in phuryn/pm-skills) into .claude/skills/pre-mortem in your project. Claude Code loads it when a task matches its description.
How do I install Pre Mortem in Codex?
Run `npx skills add phuryn/pm-skills --skill pre-mortem -a codex`. Or copy the skill folder (pm-execution/skills/pre-mortem in phuryn/pm-skills) into .agents/skills/pre-mortem in your project. Codex loads it when a task matches its description.
Can I use Pre Mortem in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add phuryn/pm-skills --skill pre-mortem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pre-mortem, .gemini/skills/pre-mortem, .github/skills/pre-mortem and .opencode/skills/pre-mortem in your project.
What does Pre Mortem need to run?
SKILL.md names no scripts, command-line tools or credentials: Pre Mortem is instructions for the agent only.
Does Pre Mortem access the network?
SKILL.md names 1 domain. As links in the text: productcompass.pm. This is read from the text; nothing was executed.
Is Pre Mortem safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pre Mortem use?
Pre Mortem is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pre Mortem use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pre Mortem?
Skills that share tags, products or a category with Pre Mortem: Prd V09 Hn Reddit Launch (mattgierhart/PRD-driven-context-engineering, 179 stars), First 1000 Users (LeoYeAI/openclaw-master-skills, 2.2k stars), Plaid (BuildGreatProducts/plaid, 217 stars) and Rfc Modeling (mirumee/nimara-ecommerce, 129 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pre Mortem?
phuryn (a GitHub user) maintains it in phuryn/pm-skills, which has 26,809 GitHub stars. The repository holds 62 skills in this directory. The repository was last updated on September 14, 2026.
Source: phuryn/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.