jira-ticket-to-gherkin

Generates Gherkin test scenarios from Jira ticket acceptance criteria via the Atlassian MCP.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/tetianna/ai-assisted-qa-automation-2 --skill jira-ticket-to-gherkin-tetianna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-ticket-to-gherkin
Source: https://github.com/tetianna/ai-assisted-qa-automation-2/tree/main/.cursor/skills/jira-ticket-to-gherkin
Command: npx skills add https://github.com/tetianna/ai-assisted-qa-automation-2 --skill jira-ticket-to-gherkin-tetianna

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about jira-ticket-to-gherkin

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

FAQPage Schema
How do I generate Gherkin test cases from a Jira ticket?▼

Reference the Jira ticket key (e.g., DS-1) and ask for test cases or scenarios. The Skill fetches the ticket via the Atlassian MCP, extracts acceptance criteria, and writes a Gherkin feature file with happy-path, negative, and edge-case scenarios.

How does the skill read Jira tickets with the Atlassian MCP?▼

It calls the getJiraIssue tool with the configured cloudId and the ticket key, requesting markdown content. Acceptance criteria are parsed from the description, custom fields, or linked Confluence pages.

Does it cover negative and edge cases or only acceptance criteria?▼

It covers all three. Every acceptance criterion gets at least one scenario, and the Skill adds negative scenarios (what must not happen) and edge cases such as boundaries, empty inputs, duplicates, and special characters.

Where are the generated Gherkin feature files saved?▼

Each feature file is saved as features/<ticket-key>.feature, for example features/DS-1.feature. The file ends with a comment block listing ambiguities and gaps found in the ticket for QA review.

What happens if the Jira ticket acceptance criteria are unclear?▼

The Skill still generates scenarios from what is available, then appends an ambiguities-and-gaps comment block to the feature file. This lists unclear or missing requirements so the QA can resolve them before automation.