plan-review

To gate design reviews before user-facing presentation, a plan review step dispatches a sub-agent to evaluate artifacts, applies mandatory gating, and writes a status marker to signal completion. This prevents unvetted work from reaching approval.

An orchestrator-level plan review is a governance step that validates designs and implementation plans before they are surfaced to users. You need it when exiting plan mode or presenting designs to ensure alignment with project goals.

To validate implementation plans before calling ExitPlanMode, dispatch a review sub-agent that selects rubrics by artifact type, validates outputs against a schema, and enforces an agent-tool guard to ensure only vetted plans proceed.

Yes, you can dispatch a single review sub-agent to evaluate design or implementation plan artifacts. The orchestrator applies artifact-type aware prompts and rubrics, providing governance signals before user-facing release.

A key limitation is that an orchestrator-level plan review works at the orchestrator level and is not itself dispatched as a sub-agent. It is designed for safe, repeatable review in multi-agent workflows rather than nested sub-agent execution.

Yes, plan review supports artifact types like design and implementation_plan. It selects review rubrics based on the specific artifact type, applying artifact-type aware prompts to evaluate the content and provide governance signals.