vc-validate-findings

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

2|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-validate-findings-marsley01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-validate-findings
Source: https://github.com/marsley01/Marsley-Portfolio-Web/tree/main/.agents/skills/vc-validate-findings
Command: npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-validate-findings-marsley01

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Plans written for AI-assisted execution often contain wrong file paths, missing steps, untested assumptions, and hidden breaking changes. This Skill runs a structured two-layer validation fan-out over a plan file so defects are caught and fixed before execution begins, producing a single net gate verdict. ## Core Features & Use Cases - Layer 1 dimension agents: Four always-on parallel checks covering infra/setup fit, test coverage, breaking changes, and security surface, each returning PASS, CONCERN, or FAIL with findings. - Layer 2 per-section feasibility agents: One agent per plan section answering four questions on mechanical feasibility, plan gaps, conflicts, and highest-risk edits, with a probe-emission rule for untestable runtime behaviors. - Net gate synthesis: Aggregates all verdicts into PASS, CONDITIONAL, or BLOCKED, generates proposed plan updates, execute-agent instructions, backlog artifacts, and a validate-contract that hands off to execution. - Use Case: Before executing a multi-package refactor plan, run the validate fan-out to discover that a listed file path is wrong and two downstream consumers are missing from the blast radius, then apply the fixes to the plan and proceed under a CONDITIONAL gate. ## Quick Start Run the validate fan-out on the plan file at process/features/my-feature/active/plan.md and present the net gate verdict with proposed plan updates.

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 spawns four Layer 1 dimension agents (infra fit, test coverage, breaking changes, security) plus one Layer 2 feasibility agent per plan section, then synthesizes all verdicts into a PASS, CONDITIONAL, or BLOCKED net gate.

What is the difference between simple mode and deep mode in plan validation?

Simple mode validates using only the plan text and current conversation context. Deep mode first loads relevant context groups, prior phase reports, and existing test files into a context bundle, and is required when the plan touches containers, infra, worker lifecycles, or has five or more blast-radius 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, and the plan must return to the planning step. CONDITIONAL applies when there are concerns but no failures, allowing execution to proceed with fixes and known gaps on record.

What happens when a plan section depends on untested runtime behavior?

The Layer 2 agent emits a VC-FEASIBILITY-PROBE-NEEDED marker with the hypothesis and cost class, then halts instead of guessing. Mechanical checks like file existence or export names never require a probe; only behaviors needing a running system or live network call do.

Does this skill decide how validation agents are executed in parallel?

No. The skill is strategy-agnostic and only defines agent role specs, prompts, and output schemas. The execution strategy (sequential, parallel subagents, workflow, or agent team) is determined separately by the vc-agent-strategy-compare skill before validation runs.