vc-validate-findings

Plan validation involves identifying all findings across infrastructure fit, test coverage, breaking changes, and security surfaces, then synthesizing them into a decisive gate status. This skill orchestrates a two-layer validation fan-out to generate a complete execution contract with proposed updates.

A validate gate status in multi-agent automation is a synthesized checkpoint that determines if a plan is safe to execute. It categorizes the net result as PASS, CONDITIONAL, or BLOCKED based on infrastructure, testing, and security findings, ensuring auditable execution across complex blast radii.

Assembling a Validate Menu requires extracting all Layer 1 and Layer 2 findings from your plan sections. This skill automates that extraction, probing per-section feasibility and defining dimensions like security surface and breaking changes to create a comprehensive validation checklist.

Yes, automated validation can generate execute-agent instructions directly from plan findings. This skill synthesizes validation results into a ready-to-apply contract, outputting the final contract blocks, test gates, and next steps required for safe agent execution.

Yes, this validation workflow supports risk assessment for breaking changes by probing them as a core Layer 1 dimension. It evaluates infrastructure and setup fit alongside breaking changes to ensure safe, auditable execution across complex blast radii.

Fan-out validation for agent planning is limited by the scope of the initial plan and the defined Layer 1 and Layer 2 probes. It standardizes validation for complex blast radii but relies entirely on the accuracy of the extracted findings to generate a correct net gate status.