plan-review-gate

Spec compliance is enforced before code-quality review by configuring a two-stage gate that validates finished PLAN outcomes against the SPEC, rejecting any plan that passes tests but fails spec before it enters wave-collection.

When a plan fails spec compliance, the BLOCKING rule prevents its admission into the wave even if tests pass, triggering bounded fix-loops until the plan is corrected and successfully passes the two-stage review gate.

Gate plan execution outcomes by deploying a review mechanism at the orchestrator seam that intercepts completed plans, enforcing locked ordering and delegating final verdicts to the peer-review workflow before wave-collection begins.

Yes, peer-review is a required dependency, as the plan review gate delegates code-quality verdicts to the peer-review workflow to ensure plans meet quality criteria before being admitted into the wave-collection.

Bounded fix-loops trigger when a plan fails the spec or quality stage, allowing a limited number of correction attempts before the gate enforces a final BLOCKING verdict to prevent unqualified plans from entering wave-collection.

The best way to validate plan outcomes is using a dedicated plan review gate that enforces locked ordering, applying spec-compliance first and code-quality second, while delegating verdicts to the peer-review workflow before wave-collection.