blueprint-phase-validation

You can validate phase execution evidence and run UAT by orchestrating canonical contracts for phase.verification and phase.uat, grounding artifacts in MCP-managed state to ensure auditable, resumable quality checks.

Phase-level gap closure keeps follow-up fixes explicit and MCP-owned after verification and testing, routing remaining issues to the implemented Blueprint surface for next actions.

Start the phase validation flow by calling the phase audit command with the target phase, which audits saved summaries, verification, and UAT artifacts while providing guided follow-ups.

Yes, phase validation integrates with optional subagents to perform bounded verification and testing when available, while ensuring safe fallbacks and clear retry and repair paths if subagents are absent.

Yes, you can preserve existing execution evidence because the validation flow always writes through MCP tools, maintaining saved evidence and strict artifact persistence across resumable checks.

Avoid automated phase validation and UAT if your workflow lacks MCP-managed state or saved execution summaries, as the validation flow strictly grounds artifacts in this evidence to ensure auditable quality checks.