Identify project failure modes and generate mitigation tasks.
npx skills add https://github.com/NickCrew/claude-cortex --skill pre-mortem
Please help me install this Agent Skill. Skill: pre-mortem Source: https://github.com/NickCrew/claude-cortex/tree/main/skills/collaboration/pre_mortem Command: npx skills add https://github.com/NickCrew/claude-cortex --skill pre-mortem
This Skill helps imagine failure modes and guardrails early to prevent expensive rework later.
Conduct a 90-day pre-mortem on a new feature and list mitigations with owners.
High-intent search queries and answers about installing and using this skill.
A pre-mortem surfaces failure modes across tech, UX, org, and market dimensions before execution. Imagine your project has failed in 30, 90, or 180 days, then work backward to identify risks and dependencies that could cause that failure, enabling proactive mitigation planning.
Organize mitigations by dimension—tech, UX, org, market, and compliance—then assign effort levels and owners to each guardrail. Convert high-impact mitigations into actionable tasks with clear owners and timelines to reduce rework and stabilize execution.
Run a pre-mortem early in planning for initiatives with clear success criteria, defined risk horizons (30, 90, or 180 days), and known compliance constraints. Earlier identification of failure modes reduces expensive rework and enables structured mitigation before development begins.
Pre-mortems work best for bounded initiatives with specific horizons and defined success criteria. Projects with 30, 90, or 180-day windows and known constraints benefit most; longer-horizon initiatives may need staged pre-mortems at each milestone.
Extract 2-3 feature candidates from your mitigations, then generate actionable tasks using the prescribed Output Template. Assign each task to an owner with effort estimates so your team can execute guardrails alongside feature development.
Analyze tech, UX, org, market, and compliance dimensions to uncover failure modes. This structured approach ensures you catch infrastructure brittleness, user experience gaps, organizational blockers, market timing risks, and regulatory constraints before launch.
qa-amanDraft comprehensive BRDs from user input with objectives, scope, constraints, and risks.
looselyorganizedExecute development features with branch isolation and progress tracking.
rysweetAutomates backlog prioritization, delegation, coordination, and roadmap strategy for software workflows.
mgd34msuIdentify, evaluate, and mitigate software development risks using pre-mortems and risk matrices.
