test-cases

Generates traceable UT, IT, E2E, and Journey test case documents from requirements.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/ab300819/keel-workflow --skill test-cases-ab300819
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-cases
Source: https://github.com/ab300819/keel-workflow/tree/main/skills/test-cases
Command: npx skills add https://github.com/ab300819/keel-workflow --skill test-cases-ab300819

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It turns requirement documents (features, user stories, acceptance criteria) into structured, traceable test case documentation, ensuring every acceptance criterion has at least one covering test case before development begins. ## Core Features & Use Cases - Multi-level test design: Derives unit (UT), integration (IT), end-to-end (E2E), and cross-story user journey (Journey) test cases from acceptance criteria, with standardized ID numbering. - Traceability matrix: Produces a requirement-to-test traceability matrix (F → US → AC → test IDs) with coverage status tracking and commit-based change-source anchoring. - Batched generation with quality anchors: Designs cases feature-by-feature, using the first batch as a quality anchor to keep later batches equally detailed, plus automated self-checks against an AC quality rubric. - Use Case: After finishing a requirements document for a user authentication feature, run the skill to produce 03-test-cases.md plus split UT/IT/E2E files with a full traceability matrix, ready for task breakdown. ## Quick Start Ask the assistant to design test cases from the existing requirements document by running the test-cases skill.

Frequently Asked Questions about test-cases

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

FAQPage Schema
How do I design test cases from a requirements document?

Provide a requirements document with features, user stories, and acceptance criteria, then run the skill. It derives UT, IT, E2E, and Journey cases per acceptance criterion and writes them to docs/devdocs/03-test-cases.md with split detail files.

What is the difference between E2E tests and user journey tests?

An E2E test validates the complete interaction of a single user story, while a Journey test chains two or more user stories to verify a cross-feature business flow and state passing between steps.

How does requirement-to-test traceability work?

Each test case carries a numbered ID (UT-XXX, IT-XXX, E2E-XXX, Journey-XXX) linked to its acceptance criterion. A traceability matrix maps F → US → AC → tests with coverage status, and change sources are recorded as repository@commit references.

Can this skill write or run actual test code?

No. It only produces test case design documents; writing implementation or test code is explicitly forbidden in this phase. Use the dev-workflow skill for coding and test-run for executing suites.

What inputs are required before generating test cases?

It expects docs/devdocs/01-requirements.md and preferably 02-system-design.md for interface signatures and module boundaries. If these are missing, it recommends running the preceding pipeline stages first.

When should small projects skip document splitting?

When there are 15 or fewer test cases and the document stays under 200 lines, everything can be merged into a single 03-test-cases.md file instead of separate UT, IT, and E2E files.