Codex Adversarial Plan Review

Overview

Red-team a plan before execution. The goal is to find blocking flaws while changes are still cheap: stale paths, unsupported assumptions, missing validation, rollback gaps, stakeholder gaps, and contradictions with prior evidence.

Workflow

1. Read the plan, success criteria, failure criteria, out-of-scope boundaries, repo map, evidence catalog, assumption ledger, dead ends, probes, and verification plan.
2. Select review lenses: software, business, or mixed.
3. Check whether every plan step is evidence-backed, ordered safely, and verifiable.
4. Classify findings as BLOCKING, IMPORTANT, or NOTE.
5. If blockers exist, revise the source plan or tell the user exactly what decision/evidence is missing.
6. Return the review in conversation. Write a review artifact only when the user explicitly requests one, and place it in the active session folder or another user-approved destination.

Native Plan Mode