insight-explore

# /explore Divergent thinking — generate 3+ implementation options, then converge on a recommendation. Produces options, not plans. > **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. > **Brainstorming Protocol — explore before committing.** `/insight-explore` generates alternatives (divergent). `/insight-assess` evaluates them (convergent). `/plan-create` designs the chosen approach. ## Phase 1 — Divergence 1. **Analyze constraints** — what are we optimizing for? What are the hard requirements vs. preferences? 2. **Option A: The Standard Pattern** — the obvious, well-trodden approach. What would most engineers reach for first? 3. **Option B: The Performance Way** — optimized for speed, scale, or efficiency. Possibly more complex. 4. **Option C: The Minimalist** — YAGNI. Smallest footprint that still solves the problem. Additional options may be added if the problem space warrants them (e.g., event-driven, type-safe, or zero-dependency variants). ## Phase 2 — Convergence Compare all options across: - **DX** — developer experience, API ergonomics, debuggability - **Robustness** — error handling, edge case coverage, failure modes - **Timeline fit** — how long does each take to implement and validate? - **Alignment** — does it match existing patterns and coding standards in the repo? ## Ph...