analyze-premortemlisted

# /analyze:premortem Forward-looking imagined-failure sub-command in the `/analyze` cluster. Loads and runs the [`premortem`](../../../../skills/premortem/SKILL.md) skill. ## Instructions ### 1. Gather the plan to stress-test Ask the user (in their language) for: - A one-sentence summary of the plan: *"We are doing X for outcome Y, touching Z."* - The prospective-failure horizon (default: 6 months post-launch). - Any known constraints, irreversibilities, or high-coordination surfaces worth front-loading. If the plan cannot be summarised in one sentence, stop and ask for scope clarification before proceeding. An un-summarisable plan is not reviewable. ### 2. Run the premortem skill Delegate to [`premortem`](../../../../skills/premortem/SKILL.md) verbatim: 1. **Set the prospective-failure frame** — "Assume total failure at horizon H. What went wrong?" 2. **Enumerate failure stories** — cover people, process, technical, external, and timing angles. Each story is a short narrative in past tense. Invoke `adversarial-review` to attack the plan's assumptions. Invoke `risk-officer` to assign L × I scores — do not re-implement L × I inline. 3. **Derive early-warning signals and preventive guardrails** — one observable signal and one actionable guardrail per top failure mode. If no practical guardrail exists, mark it `accept` with rationale. ### 3. Optional memory write-back If the analysis surfaces a pattern worth preserving for future plans: 1. De