skills / business

pre-mortem

what it does

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.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“We're launching meal-kit delivery in Rivertown on November 16. What could go wrong?”

Source material given with the request

- Launch-week forecast: 1,100 orders a day. - Drivers hired: 40. Each driver can complete about 18 deliveries a day. - Cold storage: one supplier, Frostline Storage. No backup arranged. - Launch promo: 50% off the first box, advertised on local radio from Nov 9.
with the skill
## Pre-Mortem Analysis: Rivertown Meal-Kit Delivery **Failure scenario:** It’s late November. The launch attracted customers, but orders arrived late—or not at all. Cold-storage disruptions threatened food safety, refunds erased promotional revenue, and first-time customers didn’t return. **The clearest risk is already measurable: you have delivery capacity for only 65% of forecast demand.** Resolve that before the radio campaign starts on November 9. ### Tigers (Real Risks) | Risk | Urgency | Why it matters | |---|---|---| | **Delivery capacity falls short by 380 orders daily** | **Launch-Blocking** | Forty drivers × 18 deliveries = **720 deliveries/day**, against 1,100 forecast orders. You need at least **62 drivers** just to meet forecast, with almost no buffer for absence, traffic, or failed deliveries. | | **Frostline is a single point of failure** | **Launch-Blocking** | An outage, temperature excursion, or capacity shortfall could leave you unable to store or dispatch food safely. No fallback is arranged. | | **The promotion creates demand you cannot fulfill** | **Launch-Blocking** | Radio advertising begins a week before launch. The 50% discount may increase demand beyond forecast, while advertising cannot be withdrawn instantly. Uncapped orders could turn a capacity problem into a reputational crisis. | | **Forecast delivery productivity may not hold in practice** | **Launch-Blocking: validate assumption** | “About 18 deliveries” may exclude loading, breaks, difficult addresses, route distances, and launch-day confusion. Even your current 720/day estimate may be optimistic. | | **Exceptions overwhelm customer support** | **Fast-Follow; minimum readiness before launch** | Late deliveries, substitutions, refunds, and missing boxes could generate concentrated support demand. Have basic resolution procedures ready before launch; expand staffing against observed volume. | ### Paper Tigers (Overblown Concerns) - **“We must serve every Rivertown
Show the rest (25 more lines)
neighborhood on day one.”** A smaller delivery area with reliable service is safer than broad coverage with predictable failures. - **“We need an expensive, fully duplicated cold-storage operation.”** Not necessarily. You need a credible, tested contingency—potentially reserved emergency capacity or qualified refrigerated transport—not necessarily a second permanent facility. - **“A sellout means the launch failed.”** Transparent order limits and a waitlist are preferable to taking payment for boxes you cannot reliably deliver. ### Elephants (Unspoken Worries) - **Does the discounted first box make economic sense?** Calculate contribution after ingredients, packaging, storage, delivery, marketing, and likely refunds. Model how many full-price repeat purchases recover acquisition costs. - **Is 1,100 orders/day a promotion-adjusted forecast?** Establish whether it includes radio-driven demand, and model a higher-demand case. - **Has the whole cold chain been validated?** Storage is only one link. Verify packing, loading, transit time, doorstep exposure, temperature monitoring, and rejection procedures. - **Are food-safety and operational approvals complete?** Confirm applicable permits, supplier controls, allergen labeling, and recall readiness. Missing required approvals would become launch blockers. ### Action Plans for Launch-Blocking Tigers *Proposed deadlines below work backward from November 16; no launch year was supplied.* | Risk | Mitigation and decision criterion | Owner | Due date | |---|---|---|---| | Delivery shortfall | Secure additional qualified drivers or contracted capacity, or cap daily orders. **62 drivers is the mathematical minimum; approximately 72 would support 1,100 orders at 85% of nominal capacity.** Validate the buffer operationally. | Delivery Operations lead | **Nov 8**, before radio begins | | Frostline dependency | Confirm contracted capacity and operating hours; arrange qualified fallback storage/transport. Document transfer triggers, response times, and safe product-disposal rules. | Supply Chain + Food Safety leads | **Nov 8** | | Uncontrolled promotional demand | Enforce checkout limits by date and delivery area. Add a waitlist and clear availability terms. Align radio messaging with actual capacity; defer or reduce advertising if readiness is insufficient. | Marketing + Product + Operations | **Nov 8** | | Unproven delivery rate | Run representative timed routes, including loading and handoff. Set order caps using demonstrated throughput and safe transit limits—not the hiring plan alone. | Delivery Operations + Food Safety | **Nov 6**; final rehearsal **Nov 13** | **Launch recommendation:** Do not accept 1,100 daily orders on the current plan. Before November 9, either secure and validate more capacity or explicitly limit demand. Hold a final go/no-go review on November 13. *Suggested Markdown filename: `PreMortem-Rivertown-Meal-Kit-[date].md`. I can provide the document here, but cannot save a file from this chat.*
without
The biggest risk is that **you already have a delivery-capacity gap before accounting for launch-day problems or promo-driven demand.** ### Main failure points | Risk | What could go wrong | What to do before launch | |---|---|---| | **Not enough delivery capacity** | 40 drivers × 18 deliveries = **720 deliveries/day**, against 1,100 forecast orders. That leaves **380 orders/day unserved—about 35% of demand**. Late deliveries can then spill into the next day. | You need **at least 62 drivers total** at that productivity—**22 more than hired**—just to cover the forecast, with virtually no buffer. Secure additional capacity or cap orders below verified capacity. | | **Promo demand overwhelms an already constrained operation** | The 50%-off offer may push demand above forecast, especially if customers concentrate on the same delivery dates. Radio ads begin November 9, a week before launch. | Confirm whether the 1,100-order forecast includes the promo. Before ads start, introduce date-specific order limits, clear availability messaging, and a waitlist. Make sure advertised terms match actual availability. | | **Cold-storage single point of failure** | A Frostline outage, capacity shortage, refrigeration failure, or access delay could disrupt the entire launch. | Confirm reserved capacity, operating hours, temperature monitoring, and incident procedures. Arrange a qualified backup facility and refrigerated transfer option. | | **Late deliveries become a food-safety problem** | Delays can extend time outside controlled refrigeration. Packaging alone may not keep food safe through a prolonged route or failed delivery. | Validate packaging against expected route durations and conditions. Set temperature-control requirements, maximum transit times, and clear hold/discard rules. Never deliver food whose safety is uncertain. | | **“18 deliveries/day” proves optimistic** | New routes, apartment access, parking, loading queues, driver no-shows, and failed deliveries can
Show the rest (12 more lines)
reduce throughput. At **15 deliveries per driver**, capacity falls to **600/day**. | Run realistic route trials, including loading and handoff time. Plan with demonstrated throughput and keep standby coverage. | | **Other launch bottlenecks emerge** | Picking, packing, ingredients, dispatch, or customer support may not support 1,100 orders even if delivery is fixed. Refunds and replacements could compound the workload. | Test the full order-to-door process at expected peak volume. Confirm staffing, supplies, quality checks, and support escalation capacity. | | **The discount magnifies losses and reputational damage** | Half-price boxes, extra delivery costs, refunds, and replacements could make acquisition expensive. A poor first experience may prevent repeat purchases. | Model contribution margin and cash needs under normal and disrupted scenarios. Prepare proactive delay notifications and a consistent refund/replacement policy. | ### Immediate priorities 1. **Resolve the 380-delivery daily shortfall.** Do not accept 1,100 daily commitments against a 720-delivery plan. 2. **Before November 9, align the radio offer with real capacity.** Use capped delivery slots rather than unrestricted launch demand. 3. **Remove the cold-storage single point of failure** and validate end-to-end food-safety controls. 4. **Set a go/no-go checkpoint before November 16**, based on tested delivery throughput, confirmed storage, staffing, and fulfillment readiness. **Bottom line:** Unless capacity changes, a smaller, capped launch is safer than the planned volume. More marketing would currently amplify the operational problem rather than solve it.

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 3 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 3 Nov 2026

The tasks

written by Carte Blanche
internal-tool-cutover

“Engineering is rolling out our new in-house support tool next month. Can you stress-test the plan?”

invoice-migration

“We launch in two weeks. Run a pre-mortem on this plan.”

meal-kit-city-launch

“We're launching meal-kit delivery in Rivertown on November 16. What could go wrong?”

per-seat-pricing

“We're switching from $299/month flat to $25 per seat per month on January 1. Poke holes in it.”

worry-list-triage

“Here's our launch plan and the team's worry list. Which of these should we actually worry about?”

Install

Download the .zip and unzip it. Put its files, in a folder named pre-mortem, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.