pre-mortemlisted

# Pre-Mortem Skill > **Purpose:** Is this plan/spec good enough to implement? > **Mandatory for 3+ issue epics.** Pre-mortem is enforced by hook when `$crank` is invoked on epics with 3+ child issues. 6/6 consecutive positive ROI. Bypass: `--skip-pre-mortem` flag or `AGENTOPS_SKIP_PRE_MORTEM_GATE=1`. Run `$council validate` on a plan or spec to get multi-model judgment before committing to implementation. --- ## Quick Start ```bash $pre-mortem # validates most recent plan (inline, no spawning) $pre-mortem path/to/PLAN.md # validates specific plan (inline) $pre-mortem --deep path/to/SPEC.md # 4 judges (thorough review, spawns agents) $pre-mortem --mixed path/to/PLAN.md # cross-vendor (Claude + Codex) $pre-mortem --preset=architecture path/to/PLAN.md # architecture-focused review $pre-mortem --explorers=3 path/to/SPEC.md # deep investigation of plan $pre-mortem --debate path/to/PLAN.md # two-round adversarial review ``` --- ## Execution Steps ### Step 1: Find the Plan/Spec **If path provided:** Use it directly. **If no path:** Find most recent plan: ```bash ls -lt .agents/plans/ 2>/dev/null | head -3 ls -lt .agents/specs/ 2>/dev/null | head -3 ``` Use the most recent file. If nothing found, ask user. ### Step 1.4: Retrieve Prior Learnings (Mandatory) Before review, retrieve learnings relevant to this plan's domain: ```bash if command -v ao &>