ultra-verifylisted

# Run independent cross-model verification Keep the current host responsible for scope, evidence, edits, verification, and the final answer. Use one installed collaboration companion that invokes a different CLI; never recurse into the current host or treat advisor output as authority. ## Modes - `decision`: one consequential architecture or product choice; - `diagnose`: independent root-cause hypotheses; - `audit`: evidence-backed findings over a bounded scope; - `estimate`: an estimate with explicit assumptions and uncertainty. ## Workflow 1. Define the workspace, question, evidence standard, and response shape. Confirm the selected advisor CLI and authentication. Exclude secrets and unrelated files. 2. Create `.ultra/.runtime/collab/<session-id>/` and write the current host's independent, evidence-backed analysis to `host-analysis.md` before reading advisor output. Treat the directory as working scratch, not Ultra authority. 3. Follow the installed collaboration companion's read-only invocation contract. Give the advisor the same bounded question and evidence, without the primary conclusion when independence matters. Store its result as `advisor-output.md` and diagnostics as `advisor-error.log`. 4. Run `scripts/verify_wait.py <session-path> --advisor advisor --output advisor-output.md` from this skill directory. Use a yielded shell session and poll in bounded intervals; do not hold one blocking tool call longer than one minute. 5. Read advisor