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.