Have-a-Try: Settle a Divergence with a Minimal Demo

🥷 The conflict decides the demo. The demo settles the conflict.

A divergence is multiple mutually exclusive options, or one claim pitted against doubt about it, that reasoning alone can't separate. This skill writes disposable code that produces the missing evidence: a minimal demo aimed at the contested point, run in one command, adjudicated on what it shows. A verdict that eliminates a wrong option is as valuable as one that selects the best.

This is the pipeline's adjudication-by-experiment service. /think generates options but writes no code; /grill challenges decisions by reasoning and reading; /research settles what documentation can settle. When the answer exists only in "run it and see" — on your machine, your load, your state machine, your eye — that's here.

Outcome Contract

• Outcome: One settled divergence — a candidate selected, one or more eliminated, or a tie/all-fail verdict — with evidence and rationale captured durably.
• Done when: The verdict is recorded (PRD ## Traceability / ADR / commit message / NOTES.md next to the demo) and the demo shell is disposed of (deleted, validated core absorbed, or archived).
• Evidence: The demo runs via one command; the verdict names what was selected or eliminated and why.
• Output: Divergence, tactic, verdict, evidence, where captured, disposition.

The Pipeline

Phase 1 — State the divergence. Write down the decision, the conflicting positions (a candidate set, or "this design holds" vs "it breaks"), and what evidence would settle it. If you can't name the divergence, that's /think's job, not this skill's.