spikelisted

# /spike — prototype the options, recommend with an ADR Answer a hard "which way should we build this?" question with evidence instead of a hunch. Frame the decision, have engineers prototype **several approaches in parallel as disposable spikes**, judge them against the project's real constraints, and record the outcome as an **ADR** (Architecture Decision Record). The output is a *decision with reasoning*, not shippable code — the prototypes are throwaway. Input (**$ARGUMENTS**): the open question or decision to resolve. If empty, ask what decision is blocked. --- ## Config - `APPROACHES` = 2–4 — the distinct options to prototype (derive from the question; name them up front). - `JUDGE` = `architect` (structural/quality-attribute trade-offs) — add `security-engineer`, `performance-engineer`, or `data-scientist` as extra judges when the decision hinges on their axis. - `PROTOTYPER` = `senior-engineer`. `TIME_BOX` = keep each spike minimal — just enough to answer the question, thrown away after. `ISOLATION` = each prototype in its own throwaway worktree/branch so they don't collide and nothing lands on the base branch. - **Constraints & priorities** = from the repo (quality attributes that matter here — performance, simplicity, reversibility, team familiarity, cost) plus anything in `$ARGUMENTS`. - **ADR delivery** — `MODE` = `pr` (default) or `edit-in-place`: where the **ADR** lands. This is a different axis from `ISOLATION` above: `ISOLATION` governs the thro