vc-test-coverage-plan

Output style: Follow process/development-protocols/communication-standards.md, answer-first, plain language, no unexplained jargon, TL;DR on long responses.

Generate a TDD-first full test plan per blast radius area. Assigns all 4 test tiers with exact commands, what each proves, what it does NOT prove, and explicit resolution options for every gap.

Boundary vs vc-feasibility-test

This skill is POST-decision: the design is already chosen and you are assigning coverage tiers across a known blast radius. If instead an approach cannot be decided because a runtime/library/external mechanism is unverified, that is a PRE-decision question and belongs to vc-feasibility-test (a one-shot empirical probe producing a VIABLE/NOT-VIABLE/INCONCLUSIVE VERDICT), run before SPEC/INNOVATE locks. Do not use test tiers to answer "does this mechanism work at all?".

When To Invoke

• PLAN phase, populate the Verification Evidence section of a new plan
• VALIDATE Section III, generate the full test plan after V2 fan-out, before writing the validate-contract
• EXECUTE phase, as test gates at the end of each plan section and as a regression suite after all sections complete

Context Discovery (MANDATORY FIRST, do this before anything else)

This skill MUST NOT infer tiers, commands, or runners from training data. Before reading the plan or naming a single area:

1. Invoke vc-context-discovery to load the relevant context group files.
2. Read process/context/tests/all-tests.md and follow its downstream routing chain to the relevant deeper test docs (tests/container-e2e.md, tests/browser-automation.md, tests/live-e2e.md, etc.). The entry point is a router, not full knowledge, reading only the router and skipping the chain is insufficient.
3. Discover the existing test files inside the blast radius (real runners + real commands + real fixtures, not guesses).