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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpre-mortemExecute the skills CLI command in your project's root directory to begin installation:
Fetches pre-mortem from phuryn/pm-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate pre-mortem. Access via /pre-mortem in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
27
total installs
27
this week
9.5K
GitHub stars
0
upvotes
Run in your terminal
27
installs
27
this week
9.5K
stars
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.
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.
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:
Categorize Risks: Classify each potential failure as one of three types:
Tigers: Real problems you personally see that could derail the project
Paper Tigers: Problems others might worry about, but you don't believe in them
Elephants: Something you're not sure is a problem, but the team isn't discussing it enough
Classify Tigers by Urgency:
Launch-Blocking: Must be solved before launch
Fast-Follow: Must be solved within 30 days post-launch
Track: Monitor post-launch; solve if it becomes an issue
Create Action Plans: For every Launch-Blocking Tiger:
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
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
mattpocock/skills
pre-mortem is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for pre-mortem matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: pre-mortem is focused, and the summary matches what you get after install.
pre-mortem reduced setup friction for our internal harness; good balance of opinion and flexibility.
pre-mortem has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in pre-mortem — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend pre-mortem for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: pre-mortem is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend pre-mortem for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
pre-mortem reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 29