analyze-postmortemlisted

# /analyze:postmortem Blame-free post-mortem sub-command in the `/analyze` cluster. Loads and runs the [`blameless-post-mortem`](../../../../skills/blameless-post-mortem/SKILL.md) skill, supported by [`root-cause-frameworks`](../../../../skills/root-cause-frameworks/SKILL.md). ## Instructions ### 1. Gather the incident context Ask the user (in their language) for what is known: - Incident summary (title, affected system, start/end time, severity). - Timeline bullet points (what happened, when). - Known or suspected root cause (may be empty — that is fine; the skill will derive it in Step 3). - Any existing `incident-commander` skeleton to consume. Accept an incomplete skeleton per [`analysis-memory-loop.md § 5`](../../../../docs/contracts/analysis-memory-loop.md): a missing root cause is normal, not a blocker. ### 2. Retrieve prior incident-learnings Before drafting, call `retrieve()` over the same key-space (incident type, affected paths, decision areas) per [`analysis-memory-loop.md § 2`](../../../../docs/contracts/analysis-memory-loop.md). - **Stale entries** (age > `review_after_days`) appear in `skipped` — surface them to the user, do not silently use them. - **Match found** → note the existing entry; propose a `frequency` or `supersedes` update instead of a new candidate. - **No match** → proceed to draft a new candidate in Step 5. ### 3. Derive or confirm root cause Load [`root-cause-frameworks`](../../../../skills/root-cause-frameworks/SKILL.md) and r