generate-test-plan

Generate a prioritized test plan document from a feature spec.

23|2|Updated Mar 7, 2026

Search Tags:#testing #qa #risk-analysis #test-cases #test-plan #coverage-matrix

Ready to run

npx skills add https://github.com/kirich1409/krozov-ai-tools --skill generate-test-plan-kirich1409

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate-test-plan
Source: https://github.com/kirich1409/krozov-ai-tools/tree/main/plugins/developer-workflow/skills/generate-test-plan
Command: npx skills add https://github.com/kirich1409/krozov-ai-tools --skill generate-test-plan-kirich1409

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams, QA engineers, and developers transform a feature specification, design, or implementation into a structured, prioritized test plan document. It eliminates guesswork and ensures comprehensive coverage without executing tests.

Core Features & Use Cases

Generates a markdown test plan saved to docs/testplans/ with a canonical slug like <slug>-test-plan.md.
Includes risk analysis, a coverage matrix, and potential automation candidates to guide QA and automation efforts.
Supports phase segmentation and mappings to standard test plan templates for reuse across features.

Quick Start

Describe the feature and its acceptance criteria, and I will generate a structured test plan saved to docs/testplans/.

Frequently Asked Questions about generate-test-plan

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

FAQPage Schema

How do I generate a test plan from a feature specification?▼

A test plan from a feature spec requires describing the feature and its acceptance criteria. The system then produces a prioritized markdown document saved to the docs/testplans/ directory, including risk analysis and a coverage matrix.

What is included in a structured test plan for QA teams?▼

A structured test plan includes risk analysis, a coverage matrix, and automation candidates. It formats test cases and segments testing phases to guide QA teams, saving the output as markdown in the docs/testplans/ directory.

How do I identify automation candidates from a test plan?▼

Identifying automation candidates involves generating a structured test plan from your feature spec. The resulting document explicitly lists potential automation candidates alongside the coverage matrix and risk analysis.

Can I use a risk analysis matrix without executing tests?▼

Yes, you can generate a risk analysis matrix without executing tests. The process creates a markdown documentation file containing the matrix and coverage details, strictly generating QA documentation without running tests.

Does this test plan generator support standard templates?▼

Yes, the test plan generator supports mappings to standard test plan templates. It produces phase segmentation and structured markdown files for reuse across different features within your QA workflows.

What are the limitations of generating test plans from implementation?▼

The limitation of generating test plans from implementation is that it only produces documentation. It does not execute tests, run automation scripts, or launch applications, serving solely to output a markdown file.