Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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:

CategoryFailure ModeHow 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 ModeLikelihoodImpactPriority
...High/Med/LowHigh/Med/Low1-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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

The English summary is being prepared. Showing the original description.

MaxMiksa/Autonomous-Company3.2KUpdated Oct 21, 2026

Security-focused code review checklist and automated scanning patterns. Use when reviewing pull requests for security issues, auditing authentication/authorization code, checking for OWASP Top 10 vulnerabilities, or validating input sanitization. Covers SQL injection prevention, XSS protection, CSRF tokens, authentication flow review, secrets detection, dependency vulnerability scanning, and secure coding patterns for Python (FastAPI) and React. Does NOT cover deployment security (use docker-best-practices) or incident handling (use incident-response).

The English summary is being prepared. Showing the original description.

MaxMiksa/Autonomous-Company3.2KUpdated Oct 21, 2026

Generate personalized cold email sequences (7-14 emails) with A/B test subject lines, follow-up timing recommendations, and integrated social proof. Creates multi-touch campaigns optimized for response rates. Use when users need outbound email campaigns, sales sequences, or lead generation emails.

The English summary is being prepared. Showing the original description.

MaxMiksa/Autonomous-Company3.2KUpdated Oct 21, 2026

Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

The English summary is being prepared. Showing the original description.

MaxMiksa/Autonomous-Company3.2KUpdated Oct 21, 2026

Use this skill when users need to analyze competitors, monitor market movements, benchmark features/pricing, identify market gaps, or understand competitive positioning. Activates for "what are competitors doing," market analysis, or differentiation strategy.

The English summary is being prepared. Showing the original description.

MaxMiksa/Autonomous-Company3.2KUpdated Oct 21, 2026

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.

The English summary is being prepared. Showing the original description.

MaxMiksa/Autonomous-Company3.2KUpdated Oct 21, 2026

See all skills by MaxMiksa

Report a problem with this skill