vc-test-coverage-plan

Generate TDD-first test plans with four test tiers for blast-radius areas.

1.1k|223|Updated May 27, 2026
One-click install
npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-test-coverage-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-test-coverage-plan
Source: https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-test-coverage-plan
Command: npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-test-coverage-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning thorough test coverage for blast-radius areas is labor-intensive and error-prone; this skill automates the creation of a deterministic, TDD-first verification plan that assigns four test tiers (fully-automated, hybrid, agent-probe, known-gap) with exact commands, proofs, and explicit gap-resolution options.

Core Features & Use Cases

  • Generates a per-area test plan with all four tiers, including what each tier proves and what it does not prove.
  • Documents explicit gap-resolution options for each area, ensuring traceability and remediation paths.
  • Integrates with vc-context routing to identify blast-radius areas during PLAN/EXECUTE phases and populate verification evidence.

Quick Start

Create a TDD-first test-coverage plan for the specified blast radius area and populate the verification evidence section of the plan.

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 TDD-first test coverage plan for blast radius areas?

To create a TDD-first test coverage plan for blast radius areas, you route verification plans during PLAN/EXECUTE phases to assign four distinct test tiers: fully-automated, hybrid, agent-probe, and known-gap, each with explicit commands and proofs.

What is a blast radius test plan and when do I need it?

A blast radius test plan is a deterministic verification strategy that identifies impact areas of code changes and assigns specific test tiers with exact commands and gap-resolution options. You need it when planning thorough test coverage for complex change scopes.

How do I document verification evidence for known test gaps in my test automation strategy?

You document verification evidence for known test gaps by generating per-area table blocks with A/B/C/D resolution options and a Gap Resolution Options table during the PLAN/EXECUTE phases, ensuring traceability and explicit remediation paths.

Can I automate test tier assignment for different verification areas in my project?

Yes, you can automate test tier assignment by loading the all-tests routing chain and observing the blast-radius scope to automatically route verification plans into fully-automated, hybrid, agent-probe, and known-gap tiers for each affected area.

What's the best way to structure a verification plan that covers both automated and manual testing tiers?

The best way to structure a mixed-tier verification plan is to categorize each blast-radius area into four distinct tiers—fully-automated, hybrid, agent-probe, and known-gap—documenting what each tier proves and does not prove alongside explicit gap-resolution options.

Why does my test coverage plan lack traceability for untested blast radius areas?

Your test coverage plan lacks traceability because it does not include explicit gap-resolution options for each blast-radius area. Adding a Gap Resolution Options table with A/B/C/D resolution choices ensures every untested area has a defined remediation path.