insight-assess

# /assess Structured evaluation of an approach, decision, or implementation — assess viability across multiple dimensions and deliver a clear recommendation. > **Structured execution spec:** [`protocol.yon`](protocol.yon). Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the `@STAMP` date. > **Decision Support Protocol — convergent evaluation.** `/insight-explore` generates alternatives (divergent). `/insight-assess` evaluates them (convergent). `/insight-critique` reviews outputs (reactive). Three complementary tools. ## Phase 1 — Frame the Decision Identify what is being assessed: a specific approach, a decision between options, an implementation pattern, or an architectural direction. Load relevant context — files, docs, KIs, skills. Define what we are optimizing for and the constraints. **Gate:** cannot assess without a clear subject. If the decision cannot be framed, ask for clarification before proceeding. ## Phase 2 — Dimensional Analysis Evaluate across all relevant dimensions. Skip dimensions that don't apply. **Pros & cons** — concrete advantages and disadvantages. Cite actual code, dependencies, or patterns. No vague generalizations. If comparing multiple options, do side-by-side. **Quality assessment** — score `STRONG` / `ADEQUATE` / `WEAK` with justification on: - **Performance** — bundle size, runtime overhead, N+1 queries, render cycles - **Code qua...