create-test-plan

Generate structured Markdown test plans from project context and acceptance criteria.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-test-plan-jerelvelarde
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-test-plan
Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/create-test-plan
Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-test-plan-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automating the creation of comprehensive test plans from project context and acceptance criteria to accelerate QA readiness and release confidence.

Core Features & Use Cases

  • Generates a structured test plan document with scope, acceptance criteria reference, test pyramid distribution, and risk notes.
  • Maps each acceptance criterion to unit/integration/e2e tests, including edge cases and data requirements.
  • Produces a ready-to-edit Markdown file named using the feature slug in .chalk/docs/engineering.

Quick Start

Describe the project scope and acceptance criteria to auto-generate the first test plan.

Frequently Asked Questions about create-test-plan

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

FAQPage Schema
How do I generate a test plan from acceptance criteria?

To generate a test plan from acceptance criteria, provide your project scope and criteria to automatically produce a structured Markdown document mapping each criterion to unit, integration, and e2e tests with edge cases and data requirements.

What is test pyramid distribution in software testing?

Test pyramid distribution in software testing is the allocation of test coverage across unit, integration, and end-to-end layers. This process maps acceptance criteria to appropriate test levels to ensure balanced coverage and define risk notes.

How do I map acceptance criteria to automated tests?

You map acceptance criteria to automated tests by defining test coverage that references each criterion directly. The generated plan structures these mappings across unit, integration, and e2e levels, including necessary edge cases and data requirements.

Can I use this for feature release planning and QA cycles?

Yes, you can use this for feature release planning and QA cycles. It automates test plan generation to accelerate QA readiness and release confidence by defining test coverage, pyramid distribution, and edge cases for feature development.

What format does the generated test plan use?

The generated test plan uses a ready-to-edit Markdown file format. It includes frontmatter metadata, scope, acceptance criteria references, test pyramid distribution, and risk notes, saved using the feature slug in the docs directory.

What do I need to provide to auto-generate a test plan?

You need to provide the project scope and acceptance criteria to auto-generate a test plan. No external dependencies are required; the tool uses this context to structure test coverage, pyramid distribution, and edge cases.