plan-test-coverage

Generate a prioritized e2e-plan/coverage-plan.md with P0/P1/P2 coverage and TC-IDs.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/lespaceman/athena-workflow-marketplace --skill plan-test-coverage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-test-coverage
Source: https://github.com/lespaceman/athena-workflow-marketplace/tree/main/plugins/test-analysis/skills/plan-test-coverage
Command: npx skills add https://github.com/lespaceman/athena-workflow-marketplace --skill plan-test-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This planning skill consumes exploration evidence, existing tests, and related artifacts to produce e2e-plan/coverage-plan.md with prioritized P0/P1/P2 coverage and TC-IDs. When e2e-plan/exploratory-charter.md exists, use it as optional risk-framing context; do not require it and do not let it replace grounded exploration evidence. Use it for requests like what tests I need, coverage gaps, or what TC-IDs are missing. It plans; it does not perform the canonical exploration step and it does not write executable tests.

Core Features & Use Cases

  • Consumes exploration evidence and existing tests to generate a structured coverage plan.
  • Maps to sub-features via a feature map to ensure comprehensive coverage planning.
  • Outputs TC-IDs with P0/P1/P2 prioritization and clear risk framing when charter context exists.

Quick Start

Provide a target URL and the feature name to generate the coverage plan.

Frequently Asked Questions about plan-test-coverage

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

FAQPage Schema
How do I generate a test coverage plan from exploratory testing evidence?

To generate a test coverage plan from exploration evidence, provide existing test artifacts and a target URL. The skill consumes this data to output a prioritized e2e-plan/coverage-plan.md with structured P0/P1/P2 coverage and TC-IDs.

What is the canonical TC-ID format used for mapping e2e test coverage?

The canonical TC-ID format used for mapping e2e test coverage is TC-<FEATURE>-<NNN>. This format is automatically assigned during the planning phase to structure and prioritize your test artifacts.

How do I identify coverage gaps and missing test cases for my features?

To identify coverage gaps and missing test cases, the skill maps exploration evidence to sub-features via a feature map. This structured planning approach highlights exactly what P0/P1/P2 coverage is required and which TC-IDs are missing.

Do I need an exploratory charter to plan e2e test coverage?

You do not need an exploratory charter to plan e2e test coverage. The skill uses e2e-plan/exploratory-charter.md as optional risk-framing context if it exists, but relies primarily on grounded exploration evidence.

Does this test coverage planner write automated e2e tests?

This test coverage planner does not write automated e2e tests. It strictly produces a clear, executable coverage plan with prioritized P0/P1/P2 levels and TC-IDs, separating the planning phase from test execution.