What problem does it solve? Writing test cases from Jira tickets by hand is slow and inconsistent, and acceptance criteria often miss negative and edge-case coverage. This Skill reads a Jira ticket through the Atlassian MCP and produces a structured, reviewable Gherkin feature file that QA can approve before any Playwright code is written. ## Core Features & Use Cases - Acceptance Criteria Extraction: Fetches the ticket title, description, and every acceptance criterion from Jira using the Atlassian MCP server. - Structured Gherkin Generation: Produces one Feature per ticket with happy-path, negative, and edge-case scenarios in Given/When/Then form, tagged with @TC-NNN and AC traceability tags. - Gap Reporting: Ends each feature file with a comment block listing ambiguities and gaps found in the ticket so QA can resolve them. - Use Case: A QA engineer references ticket DS-1 and asks for test cases; the Skill reads the ticket and writes features/DS-1.feature covering all ACs plus negative and boundary scenarios. ## Quick Start Ask the assistant to generate test scenarios for Jira ticket DS-1 and it will produce a reviewable Gherkin feature file.