vc-test-coverage-plan

Generates tiered test coverage plans assigning four test tiers per blast radius area.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Planning test coverage for a change's blast radius is often ad hoc, with teams guessing which areas need automated tests, which need manual probes, and which gaps are acceptable. This Skill produces a structured, TDD-first test plan that assigns every blast radius area to one of four explicit tiers with exact commands and documented gap resolutions. ## Core Features & Use Cases - Four-Tier Assignment Waterfall: Classifies each area as fully-automated, hybrid, agent-probe, or known-gap based on whether deterministic commands, preconditions, or human judgment are required. - High-Risk Class Enforcement: Forces at least hybrid-tier coverage for auth, billing, migrations, public APIs, deploy behavior, and permission logic, with mandatory rationale for any accepted gap. - TDD Stub Generation: Emits inline failing test skeletons for every fully-automated row so execute agents have a red-first starting point. - Use Case: During a VALIDATE phase after fan-out, run this Skill against a plan file to produce per-area coverage tables, gap resolution options (write test, set up infra, accept gap, backlog), and a missing-areas table before writing the validate contract. ## Quick Start Ask the agent to generate a test coverage plan for the blast radius described in your plan file, loading the all-tests.md routing chain first.

Frequently Asked Questions about vc-test-coverage-plan

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

FAQPage Schema
How do I create a test coverage plan for a blast radius?

Invoke the Skill with a plan file path or blast radius description. It first loads the all-tests.md routing chain and discovers existing test files, then assigns each area a tier using the decision waterfall and outputs per-area tables with exact commands.

What are the four test tiers in a coverage plan?

The tiers are fully-automated (deterministic CI-runnable commands), hybrid (deterministic but requiring preconditions like a live DB), agent-probe (requires judgment that cannot be mechanically asserted), and known-gap (no test possible within the plan's scope).

When should I use vc-test-coverage-plan versus vc-feasibility-test?

Use vc-test-coverage-plan after a design decision is made to assign coverage tiers across a known blast radius. Use vc-feasibility-test before decisions lock, when an unverified runtime or library mechanism must be empirically probed for a viability verdict.

What happens if the test context files are not loaded first?

The Skill emits TIER_ASSIGNMENTS_BLOCKED and stops. It refuses to infer commands or runners from training data, requiring the all-tests.md routing chain and discovered blast-radius test files before generating any tier assignments.

Which areas require at least hybrid test coverage?

High-risk classes require a hybrid minimum: auth or identity flows, billing and credit accounting, schema migrations or destructive writes, public API changes, deploy and container behavior, and permission or trust-boundary logic.

How are known-gap areas handled in the test plan?

Each gap gets four resolution options: write a new test with effort estimate, set up required infrastructure, accept as known-gap with mandatory rationale, or create a backlog artifact. High-risk gaps need especially strong justification.