From dev-hooks
Use before committing to a non-trivial plan, design, architecture, migration, launch, or irreversible decision — especially when momentum or optimism is high and nobody has named what could go wrong. Triggers when you're about to start executing a plan, when stakes are high or the decision is hard to reverse, or when the user asks to stress-test, pressure-test, or sanity-check an approach. Not for generating ideas (that's brainstorming).
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-hooks:premortemThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A premortem is the opposite of a postmortem: imagine the plan has **already failed**, then work backwards to find out why — before you've spent anything. It surfaces failure modes and hidden assumptions that optimism hides. This is destructive stress-testing; use [[brainstorming]] when you instead need to *generate* options.
A premortem is the opposite of a postmortem: imagine the plan has already failed, then work backwards to find out why — before you've spent anything. It surfaces failure modes and hidden assumptions that optimism hides. This is destructive stress-testing; use [[brainstorming]] when you instead need to generate options.
npx claudepluginhub mickzijdel/dev-hooks --plugin writingGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.