verify

To validate a Codex plan before execution, run a plan-refinement pass against the plan file. This pre-execution verification checks the active plan to catch misalignments and ensure implementation quality when no status file exists yet.

Plan refinement is a validation pass that reviews a plan file in your workspace before execution begins. You need it when a plan exists without a status file, enabling structured verification and pre-execution quality checks.

To check ongoing work against an active plan, use implementation validation mode. This verifies execution traceability by comparing the repository workspace state with an existing plan status file to ensure correct implementation.

Yes, you can integrate recon-powered context to surface dependencies and hotspots relevant to plan verification. This context-aware review enhances the structured verification workflow across the planning and execution pipeline.

The best way to enforce structured verification for Codex plans is searching docs and plans for status artifacts, then validating or refining the active plan. This catches misalignments early and guides safe handoffs before execution.

Yes, implementation validation requires an active plan with an existing status file to verify ongoing work. If no status file exists, the workflow switches to plan refinement mode to validate the plan file before execution starts.