What problem does it solve? Turning acceptance criteria from user stories, work items, or any specification document into consistent, traceable test case documentation is slow and error-prone. This Skill automates that conversion, producing one TC-XXX markdown file per scenario with full traceability back to each criterion. ## Core Features & Use Cases - Criteria-driven test generation: Reads acceptance criteria with coded identifiers (AC-001, 1.1, R-3, etc.) from US-XXX, WI-XXX, FT-XXX artifacts or any external specification document, and generates test cases covering happy path, error, and boundary perspectives. - Standardized IEEE 29119-4 structure: Each test case follows a template with preconditions, test data, execution steps, expected results, priority, and test type (Manual, Unit, Integration, API Test, Visual Test, E2E), plus an auto-maintained index README. - Azure DevOps integration: When a project management integration is active, creates Test Case work items inside the correct Test Plan and Test Suite hierarchy via MCP, using the ADO id as the TC number. - Use Case: After writing a user story with acceptance criteria AC-001 through AC-005, ask the agent to define test cases; it interviews you about environment and test data, then produces traceable TC files under the story's test-cases/ folder. ## Quick Start Ask the agent to define test cases for US-003 following the test-define skill, covering all acceptance criteria.