analyzelisted

# /analyze Top-level orchestrator for the `/analyze` family. A **confidence-weighted suggester** — classifies the user's input by keywords, proposes a numbered-options menu ranked by fit, and routes to the chosen sub-command. Never auto-selects silently. ## Sub-commands | Sub-command | Routes to | Purpose | |---|---|---| | `/analyze:postmortem` | `analyze/postmortem/command.md` | Blame-free post-mortem after a resolved incident | | `/analyze:premortem` | `analyze/premortem/command.md` | Forward-looking imagined-failure before committing to a plan | | `/analyze:decision` | `analyze/decision/command.md` | Audit a past architectural decision (did it hold?) | | `/analyze:near-miss` | `analyze/near-miss/command.md` | Post-mortem for a near-miss (same flow, lighter severity framing) | | `/analyze:incident` | `analyze/incident/command.md` | Full incident flow: commander → RCA → post-mortem → memory candidate | ## Dispatch ### 1. Parse the argument `/analyze[:<sub>] [args]` or `/analyze <sub> [args]`. - **Explicit sub-command present** → load that sub-command's body and follow its `## Instructions` verbatim with the remaining args. - **No sub-command** → proceed to Step 2. ### 2. Confidence-weighted classification Read the user's free-text input. Score each framework by keyword match: | Keyword signals | Suggests | |---|---| | "post-mortem", "outage", "incident resolved", "was ist schiefgelaufen" | `postmortem` | | "near-miss", "almost failed", "beinahe-Vorfall", "close c