insight-adversarial
/insight-adversarial
Structured adversarial review that assembles a panel of distinct critic personas, runs each through a focused pass, and synthesizes a verdict. Personas are selected based on the nature of the target — a YON workflow gets different critics than a business plan or a UX design.
Structured execution spec:
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@STAMPdate.
Caller Options. Before executing, run the Caller Options protocol (
caller-options/SKILL.md): triage this invocation for material optionality across the venues and modes declared in front-matter; if one path clearly dominates, proceed silently; otherwise surface the options to the caller. A resolved-invocation marker means COP already ran — execute the fixed combination directly, do not re-enter COP.
How Passes Work
| Pass | What Happens |
|---|---|
| Pass 1 | Classify the target → select 4–5 personas → run each → synthesize verdict |
| Pass 2 | Check against Pass 1 findings → add 2–4 new personas not used before → re-run → delta verdict |
| Pass 3 | Final wrap-up. If all critical issues resolved or within params, declare done. Otherwise escalate. |
State tracking: at the top of each pass, list which personas were used in prior passes. New passes must not reuse them.