What problem does it solve? It bridges the gap between requirements and test automation by producing a reviewable, human-readable test case catalog before any test code exists, ensuring coverage decisions happen at design time rather than during implementation. ## Core Features & Use Cases - Test Case Catalog Generation: Derives happy-path, edge, negative, and non-functional test cases from .feature scenarios and the tech design's test strategy section, with checkable expected results. - AI Evaluation Cases: Authors eval cases in JSONL format (golden, adversarial, regression, prod-sample) for LLM features, with structural expectations and judge rubric minimums. - Explicit Non-Automation Tracking: Documents what will not be automated with reasons, owners, and expiry dates so coverage gaps are visible rather than implied. - Use Case: After finalizing SRS scenarios and a tech design, invoke /gen-testcase with a UC-ID to produce a TC catalog that /unittest and /run-test later partition and automate. ## Quick Start Run /gen-testcase with a use case ID such as UC-LOGIN-01 to generate the test case catalog from the existing scenarios and tech design.