create-test-plan

Generate structured test plans from feature requirements with acceptance criteria linkage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates structured, repeatable test plans from feature requirements to ensure coverage, traceability, and alignment with acceptance criteria.

Core Features & Use Cases

  • Generate test plans using the test pyramid (unit, integration, and end-to-end levels) and boundary value analysis.
  • Map each acceptance criterion to the appropriate test level, producing explicit test cases with happy path, boundary, and error scenarios.
  • Output a single, versioned plan file in the engineering docs folder for audit and rollout.

Quick Start

Run the test plan generator for a new feature to produce a complete plan file under .chalk/docs/engineering.

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 structured test plan from feature requirements?

To generate a structured test plan from feature requirements, this Skill automatically maps acceptance criteria to unit, integration, and end-to-end test levels, creating comprehensive coverage with happy path, boundary, and error scenarios.

What is the test pyramid and how does it apply to acceptance criteria?

The test pyramid distributes tests across unit, integration, and end-to-end levels. This Skill applies pyramid-based distribution to map each acceptance criterion to its appropriate test level, ensuring balanced regression coverage.

How do I include boundary value analysis in my test coverage?

To include boundary value analysis in your test coverage, this Skill automatically generates explicit test cases featuring boundary scenarios alongside happy path and error conditions, directly linked to your feature acceptance criteria.

Do I need to manually format test plan files for engineering audits?

No, you do not need to manually format test plan files. This Skill automatically generates a single, versioned plan file under the engineering docs path, ensuring immediate readiness for audit and rollout.

What's the best way to ensure traceability between test cases and feature requirements?

The best way to ensure traceability between test cases and feature requirements is to enforce acceptance criteria linkage, mapping each criterion to explicit unit, integration, and E2E test scenarios within a versioned plan file.