verify-plan

To verify an implementation plan before coding, you provide the plan file path to a dedicated plan-verifier agent that runs in isolation to surface verifiable risks and return a structured verdict with revision options.

Automated plan validation is a workflow step that runs a separate agent to assess a written implementation plan against design docs and known error patterns, producing a verification report with blocking decisions before execution.

You check architecture plan risks by dispatching an automated verification agent that analyzes the plan alongside design analysis and project root context, yielding a structured verdict with decision points to prevent risky changes.

Plan verification requires providing the plan file path, while the system automatically gathers associated design doc paths, design analysis, crystal file path, and project root to anchor verification decisions to plan content.

Yes, automated plan verification reduces miscommunications by validating the written implementation plan in a separate context, anchoring decisions to design references, and enabling safe incremental improvements before coding begins.

Automated plan verification is not necessary for trivial changes that do not require a written implementation plan, as the process relies on gathering design docs and project context to produce a structured verification report.