跳到正文
cccskills
免费在 GitHub 公开

pre-mortem

Review a product plan by imagining a failed launch and tracing possible causes. Separate real risks, overblown concerns, and unspoken worries, then define mitigation actions, owners, and deadlines for issues that must be resolved before launch.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

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.

查看安装方法

适用场景

  • Checking launch plans for possible failure causes
  • Separating real risks from overblown concerns
  • Surfacing assumptions the team has not discussed
  • Assigning actions and deadlines for launch blockers

包含的文件(1)

  • SKILL.md4.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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

  1. 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.

  2. 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?
  3. 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
  4. 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
  5. 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
  6. 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]
    
  7. Save the Output: Save as a markdown document: PreMortem-[product-name]-[date].md

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

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.

中文简介正在准备中。当前显示英语简介。

  • Checking whether an A/B test shows a meaningful difference
  • Reviewing sample size and test duration
  • Deciding whether to launch a tested change
phuryn/pm-skills2.7万2026年10月16日 更新

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

中文简介正在准备中。当前显示英语简介。

  • Grouping customer requests into themes
  • Selecting the top three requests for product goals
  • Considering alternatives to requested features
phuryn/pm-skills2.7万2026年10月16日 更新

Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.

中文简介正在准备中。当前显示英语简介。

  • Comparing growth options for an existing business
  • Planning expansion into new regions or customer groups
  • Evaluating new products for current customers
phuryn/pm-skills2.7万2026年10月16日 更新

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

中文简介正在准备中。当前显示英语简介。

  • Choosing the first customer segment for a new product
  • Focusing limited resources on a launch market
  • Comparing segments using interviews and customer feedback
phuryn/pm-skills2.7万2026年10月16日 更新

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

中文简介正在准备中。当前显示英语简介。

  • Checking feature assumptions before implementation
  • Planning prototype usability tests
  • Defining metrics and success thresholds for A/B tests
phuryn/pm-skills2.7万2026年10月16日 更新

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

中文简介正在准备中。当前显示英语简介。

  • Testing demand before building a new product
  • Planning landing page or waitlist experiments
  • Checking willingness to pay through pre-orders
phuryn/pm-skills2.7万2026年10月16日 更新

查看 phuryn 的全部技能

报告此技能的问题