Agent skill
premortem
Pre-mortem analysis that imagines a plan has failed, then works backward to identify causes and preventions. Use before launches, major decisions, or risky initiatives to surface hidden risks.
Install this agent skill to your Project
npx add-skill https://github.com/nicepkg/auto-company/tree/main/.claude/skills/premortem
SKILL.md
Pre-Mortem Analysis
Imagine the plan has completely failed, then work backward to identify what went wrong and how to prevent it.
Instructions
Set the scene: "It's [timeframe] in the future. This initiative was a complete disaster. Looking back, what happened?"
Generate failure scenarios without filtering for likelihood—get everything on the table first, then prioritize.
Output Format
The Plan Summarize what's being attempted and the success criteria.
Time Jump "It's [X months] later. This has failed completely. The outcome: [describe the disaster vividly]."
What Went Wrong
Generate 8-12 plausible failure causes across categories:
| Category | Failure Mode | How It Played Out |
|---|---|---|
| Execution | [What failed] | [The story of how] |
| External | [What failed] | [The story of how] |
| People | [What failed] | [The story of how] |
| Technical | [What failed] | [The story of how] |
| Assumptions | [What failed] | [The story of how] |
Risk Prioritization
| Failure Mode | Likelihood | Impact | Priority |
|---|---|---|---|
| ... | High/Med/Low | High/Med/Low | 1-5 |
Top 3 Risks & Mitigations
For each top risk:
- Risk: [Description]
- Early Warning Signs: What would indicate this is happening?
- Prevention: How to reduce likelihood
- Mitigation: How to reduce impact if it occurs
- Owner: Who's responsible for watching this?
Pre-Mortem Insights What did this exercise reveal that wasn't obvious before?
Revised Confidence After this analysis, how confident are you in success? What would increase confidence?
Guidelines
- Be vivid and specific—"the database corrupted" not "something went wrong"
- Include uncomfortable possibilities (key person leaves, competitor moves, we were wrong)
- Don't filter for "that won't happen"—the point is to surface hidden concerns
- Assign real owners to mitigations
- Look for single points of failure
$ARGUMENTS
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
micro-saas-launcher
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
deep-analysis
Analytical thinking patterns for comprehensive evaluation, code audits, security analysis, and performance reviews. Provides structured templates for thorough investigation with extended thinking support.
ux-audit-rethink
Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.
startup-financial-modeling
This skill should be used when the user asks to "create financial projections", "build a financial model", "forecast revenue", "calculate burn rate", "estimate runway", "model cash flow", or requests 3-5 year financial planning for a startup.
ph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Didn't find tool you were looking for?