cross-eval

Topics in the source

• /c-level-agents:cross-eval — Multi-Model Consensus
• When to Run
• Models Used (graceful degradation)
• Workflow
• Output Format
• Why This Matters
• Graceful Degradation
• Routing

Command: /c-level-agents:cross-eval Runs the same memo through multiple model providers and reconciles divergences. Use for high-stakes, irreversible decisions where single-model bias is too costly: M&A, major fundraises, layoffs, strategic pivots, regulatory commitments. Adapted from gstack's /codex cross-review pattern, generalized to business memos instead of code PRs. Before signing a term sheet Before announcing a layoff Before committing to a regulated market Before any decision where reversing costs > 6 months of company time When the boardroom vote was split or had a CRITICAL dissent The command tries to invoke each available model in order: 1. Claude (primary, always available) — the boardroom's native voice 2. Codex / OpenAI (if OPENAIAPIKEY or codex CLI available) 3. Gemini (if GEMINIAPIKEY or gemini CLI available) If only Claude is available, the command runs Claude-only with adversarial mode — same model, different prompt seeds — and clearly labels the output as single-model. 1. Read the memo / brief 2. Probe environment for available model CLIs / API keys 3. For each available model: Send the memo with this prompt prefix: "You are an independent C-suite reviewer. The

This is an excerpt. Refer to the complete source and its current requirements.