test-planner

Generate a coverage-aware test plan with Markdown output and JSON metadata.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/thistleknot/skills --skill test-planner-thistleknot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-planner
Source: https://github.com/thistleknot/skills/tree/main/test-planner
Command: npx skills add https://github.com/thistleknot/skills --skill test-planner-thistleknot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test planners struggle to know what to test next, how much coverage already exists, and which scenarios are missing or should be added for regressions.

Core Features & Use Cases

  • Coverage-aware subject classification: Identifies testable subjects and labels them as 🟢 GREEN, 🟡 YELLOW, or 🔴 RED based on existing coverage.
  • Scenario proposals by test level: Proposes concrete smoke/unit/integration/e2e/regression scenarios for each subject.
  • Regression-focused planning: Uses optional git diff inputs to flag and prioritize changed subjects for re-verification.

Quick Start

Use test-planner to generate a Markdown test plan for your project and have it rank subjects by 🟢/🟡/🔴 coverage status.

Frequently Asked Questions about test-planner

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

FAQPage Schema
How do I generate a coverage-aware test plan for my project?

You can generate a coverage-aware test plan by identifying testable subjects and classifying their existing test coverage as green, yellow, or red. The tool then outputs a Markdown artifact proposing concrete smoke, unit, integration, e2e, and regression scenarios.

How does regression testing work with a git diff?

Regression testing with a git diff uses an optional git ref or range input to flag and prioritize changed subjects for re-verification. This ensures your test plan focuses on scenarios that should be added for modified code.

How do I know what to test next when planning tests?

To know what to test next, the planner ranks testable subjects by green, yellow, or red coverage status. This classification highlights missing scenarios and identifies which subjects lack existing tests and require immediate attention.

Does test planning require language detection for tool selection?

Yes, coverage-aware test planning requires language detection for tool selection. The process performs test discovery to compute coverage status accurately, ensuring the generated test plan matches your project's specific testing framework.

What is the best way to propose scenarios across different test levels?

The best way to propose scenarios across test levels is to apply planning across smoke, unit, integration, e2e, and regression phases. This generates concrete scenario proposals for each identified testable subject within your project.

What format does the generated test plan output use?

The generated test plan outputs a Markdown artifact that includes structured JSON metadata and provenance. This format documents the coverage status, proposed scenarios, and regression detection details for your project.