analyze-near-misslisted

# /analyze:near-miss Near-miss analysis sub-command in the `/analyze` cluster. Uses the [`blameless-post-mortem`](../../../../skills/blameless-post-mortem/SKILL.md) skill with a near-miss framing — same structure as [`analyze:postmortem`](../postmortem/command.md) but the emphasis is on *what prevented actual impact* and *what systemic changes prevent recurrence*, not on cataloguing damage. ## Instructions ### 1. Gather the near-miss context Ask the user (in their language) for: - Event summary — what happened, what was at risk, what contained it. - Timeline bullets (what occurred, in what order). - Known trigger or suspected root cause (may be empty). - What safeguard, luck, or human action prevented full impact. Accept incomplete information; the write-up may include open items with `status: draft`. ### 2. Retrieve prior incident-learnings Before drafting, call `retrieve()` over the same key-space (affected system, incident type, decision area) per [`analysis-memory-loop.md § 2`](../../../../docs/contracts/analysis-memory-loop.md): - **Stale entries** (age > `review_after_days`) are in `skipped` — surface them; do not silently use them. - **Match found** → propose a `frequency` / `supersedes` update. - **No match** → proceed to draft a new candidate in Step 4. ### 3. Write the near-miss document Following [`blameless-post-mortem`](../../../../skills/blameless-post-mortem/SKILL.md), produce a write-up covering: 1. **Summary** — what was at risk, what contained