vc-validate-findings

Orchestrates two-layer parallel validation of implementation plans into a PASS, CONDITIONAL, or BLOCKED gate verdict.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/HyuseCS/project-c --skill vc-validate-findings-hyusecs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-validate-findings
Source: https://github.com/HyuseCS/project-c/tree/main/.claude/skills/vc-validate-findings
Command: npx skills add https://github.com/HyuseCS/project-c --skill vc-validate-findings-hyusecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Before executing a multi-section implementation plan, teams need a structured way to catch infra mismatches, missing test coverage, breaking changes, and security risks. This Skill defines the agent roles, prompts, and output schemas for a two-layer validation fan-out that produces a single net gate verdict gating execution. ## Core Features & Use Cases - Layer 1 dimension agents: Runs four parallel checks covering infra/setup fit, test coverage, breaking changes, and security surface. - Layer 2 feasibility agents: Spawns one agent per plan section to assess mechanical feasibility, plan gaps, conflicts, and highest-risk edits, with a probe-emission rule for untestable runtime behaviors. - Net gate synthesis: Aggregates all findings into PASS, CONDITIONAL, or BLOCKED with exact output tables, plan-update proposals, and execute-agent instructions. - Use Case: After drafting a plan that touches five packages and a container gateway, invoke this Skill to fan out validation agents, surface a port conflict and an unlisted downstream consumer, apply fixes to the plan, and write the validate-contract before EXECUTE. ## Quick Start Run the validate fan-out on my plan file at process/features/auth/active/login-plan.md and give me the net gate verdict.

Frequently Asked Questions about vc-validate-findings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate an implementation plan before executing it?

Invoke the validate fan-out with the plan file path. It runs four Layer 1 dimension agents plus one Layer 2 feasibility agent per plan section in parallel, then synthesizes results into a PASS, CONDITIONAL, or BLOCKED net gate.

What is the difference between Simple mode and Deep mode validation?

Simple mode validates using context already in the conversation and suits self-contained plans. Deep mode loads context group files, prior phase reports, and existing tests first, and is required when plans touch containers, infra, workers, or span 5+ packages.

When does the validation gate return BLOCKED instead of CONDITIONAL?

The gate is BLOCKED when any Layer 1 or Layer 2 agent returns a FAIL verdict. CONDITIONAL applies when there are CONCERNs but no FAILs, and PASS requires zero FAILs and zero CONCERNs.

What is a feasibility probe and when is it emitted?

A feasibility probe is emitted when a plan section depends on untested runtime behavior that cannot be verified by reading source files, such as live network responses. The agent emits VC-FEASIBILITY-PROBE-NEEDED with a cost class and halts instead of guessing.

Does this Skill decide how validation agents are executed?

No. It is strategy-agnostic and only defines agent role specs, prompts, and output schemas. The execution strategy is chosen separately by vc-agent-strategy-compare, which must run before this Skill.