test-case-generator

Generate structured test cases from spec.md acceptance criteria with 1:1 traceability.

21|5|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/aws-samples/sample-agent-greenhouse --skill test-case-generator-aws-samples
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-case-generator
Source: https://github.com/aws-samples/sample-agent-greenhouse/tree/main/src/platform_agent/plato/skills/test_case_generator
Command: npx skills add https://github.com/aws-samples/sample-agent-greenhouse --skill test-case-generator-aws-samples

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates structured test cases from spec.md acceptance criteria with 1:1 traceability to ACs.

Core Features & Use Cases

  • Reads spec.md files from developer repositories
  • Extracts AC-xxx entries and generates one test case per AC
  • Classifies test type (unit, integration, e2e) using keyword heuristics
  • Produces test cases in a standard format that traces to the original ACs

Quick Start

Run the generator against a repository containing a spec.md to produce test cases that map each AC to a TC.

Frequently Asked Questions about test-case-generator

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

FAQPage Schema
How do I generate test cases from acceptance criteria in spec.md files?

To generate test cases from acceptance criteria, the Skill reads spec.md files, extracts AC-xxx entries, and creates one structured test case per acceptance criterion with 1:1 traceability. Results are formatted in a standard test case layout mapping back to each AC.

What's the best way to ensure traceability between spec.md acceptance criteria and generated tests?

Traceability between acceptance criteria and generated tests is ensured by creating exactly one test case per AC-xxx entry found in spec.md. This 1:1 AC-to-TC mapping guarantees that every acceptance criterion has a corresponding test case linked directly to its original specification.

Do I need a specific repository structure to generate test cases from spec.md?

You need a developer repository containing a spec.md file with defined acceptance criteria. The Skill scans the repository for spec.md files, extracts AC-xxx entries, and produces test cases without requiring external dependencies or additional framework installations.

Can I automate test case generation for quality assurance without manual writing?

Automating test case generation for quality assurance is achieved by running the Skill against repositories containing spec.md files. It automatically extracts acceptance criteria, classifies each test as unit, integration, or e2e, and outputs structured test cases mapped directly to their originating ACs.

Why use keyword heuristics for test case type classification instead of manual labeling?

Keyword heuristics classify test cases as unit, integration, or e2e by analyzing text patterns in acceptance criteria, eliminating manual labeling effort. This automated approach ensures consistent test type assignment across all generated cases derived from spec.md AC-xxx entries.