blueprint-review

Blueprint phase review orchestration coordinates end-to-end peer reviews across project phases, capturing phase-scoped evidence to produce durable, standardized review artifacts. It applies structured routing to keep security, code, and UI reviews aligned with phase goals.

You generate standardized code review artifacts by running an end-to-end blueprint review cycle using current phase evidence. This process applies canonical contract compliance and MCP-backed persistence to output durable, evidence-backed review files.

Yes, blueprint-review applies unified orchestration to security, UI, code, audit, and peer-review workflows. It ensures phase-scoped evidence is captured and persisted across these diverse review types to support risk assessment.

The best way to persist peer-review evidence is using MCP-backed persistence to generate canonical XX-REVIEW.md artifacts. This ensures phase outcomes are durably stored, structurally compliant, and explicitly support downstream risk handling.

Yes, you need required MCP tools and canonical contract templates to produce standardized review artifacts. The orchestration process satisfies these required inputs to ensure phase-scoped evidence is captured and persisted correctly.

You should avoid automated blueprint review orchestration when a project phase lacks sufficient evidence or required MCP inputs. Without canonical contract compliance and phase-scoped data, the process cannot produce durable, standardized review artifacts.