Spike

You can't compare approaches in the abstract. Implement each one, see how they feel in real code, then decide. This removes speculation and replaces it with evidence.

Why This Works

Design discussions stall on hypotheticals. Implementing each approach takes the guesswork out. You get exact line counts, real dependency changes, actual lint/compile errors that reveal hidden constraints, and the visceral feel of reading the code.

On Activation

1. Select — Choose N approaches to implement.
2. Prepare — Identify the base branch and files to modify.
3. Implement — One branch per approach, fully working.
4. Verify — Each branch compiles and passes lint.
5. Compare — Side-by-side table of discriminating dimensions.

Phase 1: Select

Identify exactly N approaches. Sources include /synthesize output, /brainstorm rankings, a user-specified list, or freeform description.