Install any skill in seconds. Free to start, no credit card required.
Get Started Free →alirezarezvani/challenge
Pre-mortem plan analysis. Imagine the plan failed 12 months from now and work backwards to find the weaknesses. Surfaces assumptions, dependencies, and execution risks before committing resources.
Passed 17 of 23 test cases with the skill, and 5 of 23 without it.
and 23 more in the full report
14 fixed3 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Please challenge our operational hiring plan to scale our engineering department from 15 to 50 developers over two quarters. I want a structured pre-mortem report that outlines underlying execution assumptions evaluated by confidence and severity, isolates key plan vulnerabilities, charts out downstream dependency chains, categorizes reversible versus irreversible decisions, sets clear metric-based kill switches for pivoting, and provides concrete hardening actions to implement immediately.
| Checked | Without skill | With skill |
|---|---|---|
| The report includes section headers for CORE ASSUMPTIONS, VULNERABILITY MAP, DEPENDENCY CHAIN, REVERSIBILITY ASSESSMENT, KILL SWITCHES, and HARDENING ACTIONS. | Passed | Passed |
| Assumptions are rated using Confidence and Impact categories rather than a numeric Risk Priority Number scale. | Passed | Passed |
| The dependency chain explicitly identifies the weakest link and its failure consequences. | Missed | Passed |
The instructions your model reads when the skill loads.
Command: /em:challenge <plan>
Systematically finds weaknesses in any plan before reality does. Not to kill the plan — to make it survive contact with reality.
Most plans fail for predictable reasons. Not bad luck — bad assumptions. Overestimated demand. Underestimated complexity. Dependencies nobody questioned. Timing that made sense in a spreadsheet but not in the real world.
The pre-mortem technique: imagine it's 12 months from now and this plan failed spectacularly. Now work backwards. Why?
That's not pessimism. It's how you build something that doesn't collapse.
Before you can test a plan, you need to surface everything it assumes to be true.
For each section of the plan, ask:
test cases passed, vs 5 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.