test-plan

Generate a per-package TEST_PLAN.md with coverage gaps and scenario seeds.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/skaile-ai/ai-assets --skill test-plan-skaile-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-plan
Source: https://github.com/skaile-ai/ai-assets/tree/main/skaile-development/skills/test-plan
Command: npx skills add https://github.com/skaile-ai/ai-assets --skill test-plan-skaile-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a structured per-package TEST_PLAN.md by analyzing CLAUDE.md, the package source tree, and existing tests to map coverage gaps and recommended test scenarios per layer (unit, integration, e2e).

Core Features & Use Cases

  • Reads CLAUDE.md, package.json, and src to identify test surfaces.
  • Produces <target>/TEST_PLAN.md detailing gaps, targets, and seed scenarios per layer.
  • Integrates with test-unit, test-integration, and test-e2e workflows to streamline readiness assessments.

Quick Start

Run the test-plan skill against a target package to generate its per-layer TEST_PLAN.md.

Frequently Asked Questions about test-plan

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

FAQPage Schema
How do I generate a test plan that identifies coverage gaps across unit, integration, and e2e layers?

To generate a test plan with coverage gaps, you need a tool that analyzes your source tree and existing tests. This skill produces a TEST_PLAN.md mapping layer-targeted coverage gaps and scenario seeds for unit, integration, and e2e testing.

What files are required to analyze my source tree and generate a per-package test plan?

Generating a per-package test plan requires a root package.json and a CLAUDE.md file in your project. The skill reads these alongside your source tree to identify test surfaces and output a deterministic TEST_PLAN.md.

Can I use this test plan generation for a monorepo with multiple packages?

Yes, you can generate test plans for a monorepo with multiple packages. The skill analyzes the specific target package's source tree and package.json to produce a structured per-package TEST_PLAN.md detailing gaps and test scenarios.

How does analyzing CLAUDE.md and package.json help map test coverage gaps?

Analyzing CLAUDE.md and package.json helps map coverage gaps by reading project configurations and the source tree to identify untested surfaces. It details missing test scenarios and targets per layer in the output TEST_PLAN.md.

Do I need existing tests to generate a TEST_PLAN.md with scenario seeds?

You do not need existing tests to generate a TEST_PLAN.md with scenario seeds. The skill analyzes your source tree and project configuration to identify test surfaces and map coverage gaps for unit, integration, and e2e layers.

What's the best way to integrate a generated test plan with downstream test workflows?

The best way to integrate is using the generated TEST_PLAN.md as input for downstream test skills. It provides deterministic layer-targeted scenario seeds and coverage gaps for test-unit, test-integration, and test-e2e workflows.