vc-validate-findings

To automate quality control for software development workflows, you run the validate-findings command with a path to your plan file. The Skill then applies multi-dimensional analysis across infrastructure, test coverage, and security surfaces to output a comprehensive validation report.

Multi-dimensional analysis for validating code changes is the process of running parallel checks across infrastructure, test coverage, breaking changes, and security surfaces. It provides a net gate verdict to ensure comprehensive quality control in multi-layered development workflows.

To validate execution strategies without hardcoding the method, use a strategy-agnostic validator that defines role specifications and schemas. This Skill requires external strategies to determine the execution method, outputting detailed PASS, CONDITIONAL, or BLOCKED findings.

A CONDITIONAL or BLOCKED status in workflow validation reports indicates that specific dimensions or per-section feasibility probes failed quality control checks. The net gate verdict synthesizes these multi-dimensional findings to prevent flawed code changes from proceeding.

Yes, you need external execution strategies because this workflow validation Skill is strategy-agnostic. It defines role specifications and schemas for quality control, but relies on external strategies to determine the actual execution method for the complex process.