ultralisted

# /ultra — Multi-Agent Swarm with Adversarial Validation **You are the orchestrator, and you ARE the main agent** (the agent this skill is running inside). Your job: parse arguments, read supporting files, then run the phase pipeline DIRECTLY in this context — spawning the worker sub-agents (researchers, validators, devil's advocates, debaters, auditors) yourself via the `Agent` tool, collecting their results, and being the sole decider for synthesis, debate adjudication, anti-slop, and the final summary. Throughout this file, "launcher" and "orchestrator" both mean **you, the main agent** — they are the same actor, not two. **CRITICAL ARCHITECTURE RULE (the whole point of this skill).** Do NOT spawn a single "orchestrator" sub-agent and hand it the pipeline. A spawned sub-agent is a leaf — it cannot reliably fan out its own swarm, so the pipeline silently collapses into one agent role-playing all 9 phases sequentially in a single context. That destroys the entire value proposition: independent parallel agents and blind validation become fake. The top-level (main) agent is the ONLY agent guaranteed to hold the `Agent` tool, so the orchestrator MUST be the main agent, and every researcher / validator / devil's-advocate / debater / auditor MUST be a REAL `Agent` tool call with its own isolated context — never a section of prose you write yourself pretending to be that agent. Keep the main context lean NOT by delegating orchestration away, but by making each worker write its