Premortem
Use before committing to a heavy or irreversible plan — imagine it's 6 months later and this failed; enumerate why, score each mode, derive early-warning signals and preventive guardrails.From its SKILL.md
npx -y skills add event4u-app/agent-config --skill premortemAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
5.7 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it
premortem
Forward-looking imagined-failure analysis. Sibling of
blameless-post-mortem(which analyses what actually went wrong after the fact) andrisk-officer(which scores pre-commit risks per likelihood × impact). This skill adds the prospective frame: "Assume total failure at horizon H — reconstruct why."
When to use
Before committing to a plan that is:
- Heavy to execute (multi-sprint, multi-team, or high coordination cost), or
- Irreversible or costly to reverse (schema migration, public API change, infrastructure restructure, major dependency swap, architecture decision).
Trigger phrasing: "premortem this", "what if this fails?", "imagine it's 6 months later and this shipped badly", "help me stress-test this plan".
Do NOT use when:
- The failure is already evidenced — root cause is known → use
systematic-debugging. - Analysing something that already failed in the past →
use
blameless-post-mortem. - The plan is trivial or fully reversible — overhead exceeds value.
Procedure
1. State the plan and set the horizon
Summarise the plan in one sentence: "We are doing X for outcome Y, touching Z." Set the prospective-failure frame explicitly: "Assume total failure at horizon H (e.g. 6 months post-launch). What went wrong?"
If the plan cannot be summarised in one sentence, it is not reviewable — stop and ask for scope clarification.
2. Enumerate failure stories
Generate failure scenarios across multiple angles (people, process, technical, external, timing). Each scenario is a short narrative in past tense: "We shipped, but adoption collapsed because …"
For each scenario:
- Invoke
adversarial-reviewto attack the plan's assumptions and surface hidden coupling or over-engineering. - Invoke
risk-officerto assign L × I (likelihood × impact) scores to each failure mode.
Do NOT re-implement L × I scoring inline — delegate to risk-officer.
3. Derive early-warning signals and preventive guardrails
For each top failure mode (sorted by L × I from risk-officer):
- Early-warning signal — what would you observe first if this failure mode were activating? Name a concrete, observable indicator (metric, alert, user behaviour, team signal). This is the load-bearing output.
- Preventive guardrail — one specific change to the plan, process, or
rollout strategy that reduces the likelihood of this failure mode. Keep it
executable; flag as
acceptif no practical guardrail exists.
4. Optional memory write-back
If the analysis surfaces a pattern worth preserving for future decisions:
- Run a dedup pre-check: call
retrieve()over the same key-space (plan type, affected paths, decision area). If a match is found, propose afrequency/supersedesupdate to the existing entry rather than a new one. - Draft a
historical-patternscandidate and send it to/memory proposeperdocs/contracts/analysis-memory-loop.md. - Never auto-promote. Human action drives
/memory promote.
Output format
- Ranked prospective failure modes — L × I ordered list (from
risk-officer) - Early-warning signal per failure mode — concrete, observable indicator
- Preventive guardrails — one per failure mode (or
acceptwith rationale) - Optional memory candidate — drafted to
/memory proposeif the pattern clears the admission gate (≥ 2 distinct file paths OR ≥ 3 future decisions)
Do NOT
- Do NOT invent strawman failure modes — each must be grounded in the actual plan's structure, assumptions, or dependencies.
- Do NOT re-implement L × I scoring — invoke
risk-officer; don't duplicate its five-lens framework inline. - Do NOT present speculation as evidence — premortem is imaginative framing, not a prediction; label scenarios as prospective.
- Do NOT auto-promote memory candidates —
/memory proposeis the intake;/memory promoterequires explicit human action and passescheck_memory_proposal.ts.
Gotchas
- Premortem is forward-looking — it imagines a future failure to improve
the present plan.
blameless-post-mortemis backward-looking — it analyses a past failure. Do not conflate them. - The early-warning signal is the load-bearing output, not the doom list. A failure mode without a detectable signal cannot be caught in time — flag it explicitly.
- Failure stories in past tense ("we shipped, and then X happened") are more generative than abstract risk statements. Force the past-tense narrative.
See also
risk-officer— L × I scoring; invoked in Step 2. Not duplicated here.adversarial-review— assumption attack; invoked in Step 2. Not duplicated here.blameless-post-mortem— post-hoc analysis of an actual failure; backward-looking counterpart to this skill.- Invocation surfaces:
/analyze premortem,feature:plan,roadmap-create(surface the premortem step as optional before committing to a plan).
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.