premortem
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add whyashthakker/estack --skill premortemCompatible with
Supported agents
Run a premortem on a plan, launch, migration, or change before it ships.
Assume it already failed, list the most likely reasons, rank them by likelihood and cost, and turn the top risks into checks, guards, or a rollback plan.
Use when the user says "premortem", "what could go wrong", "stress test this plan", "is this safe to ship", or before a launch, a data migration, a pricing change, a big refactor, or anything costly to undo.
| name | premortem |
| description | Run a premortem on a plan, launch, migration, or change before it ships. Assume it already failed, list the most likely reasons, rank them by likelihood and cost, and turn the top risks into checks, guards, or a rollback plan. Use when the user says "premortem", "what could go wrong", "stress test this plan", "is this safe to ship", or before a launch, a data migration, a pricing change, a big refactor, or anything costly to undo. |
Goal: find the failure before your users do. People are better at explaining a failure than predicting one, so start from the failure.
In three lines: what will change, who it affects, and how you will know it worked (one measurable signal). If you cannot write the signal, that is the first risk.
"It is 30 days later. This failed badly. Why?" Write 8 to 12 causes. Cover each area:
Read the real code and config for each one you suspect. A risk you checked beats a risk you imagined.
For each cause: likelihood (low, med, high), cost if it happens (low, med, high), and whether it is easy to undo. Keep the top 3 to 5: high on two of the three.
For each top risk, one of:
A short table (risk, likelihood, cost, action, owner), then a go / go-with-fixes / stop call with one line of reason. Do not make the fixes in this skill unless the user asks. Ship after with ship.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpremortemExecute the skills CLI command in your project's root directory to begin installation:
epx add whyashthakker/estack --skill premortemFetches premortem from whyashthakker/estack and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/premortem
Restart Cursor to activate premortem. Access via /premortemin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
premortem is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: premortem is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in premortem — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
premortem fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for premortem matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for premortem matched our evaluation — installs cleanly and behaves as described in the markdown.
premortem has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: premortem is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: premortem is focused, and the summary matches what you get after install.
premortem is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 36