Can I save the conversion to a specific file?

Yes, you can use the optional --output flag followed by your desired file path to save the converted specification directly to your workspace.

Does this skill validate Gherkin syntax?

Yes, the conversion process includes a validation step to ensure the resulting Gherkin content follows standard BDD syntax and structural best practices.

Can I convert my existing .feature files back to markdown specs?

Absolutely. The skill is bi-directional, allowing you to convert Gherkin scenarios into canonical specifications or EARS requirements for documentation purposes.

How do I specify the target format during conversion?

Use the --to argument followed by the desired format, such as 'gherkin', 'feature', 'canonical', 'ears', or 'inline' when running the command.

What formats are supported for conversion?

The skill supports conversions between Gherkin (.feature files), EARS (Easy Approach to Requirements Syntax), canonical markdown specifications, and inline acceptance criteria.

Gherkin BDD Converter

Name: Gherkin BDD Converter
Author: melodic-software

bymelodic-software

•

Security & Testing

Converts between Gherkin/BDD scenarios and various specification formats like EARS, canonical markdown, or inline acceptance criteria.

The gherkin-convert skill streamlines the transition between technical requirements and behavior-driven development (BDD) by automating format conversions. It allows developers and product owners to transform Easy Approach to Requirements Syntax (EARS) or canonical specifications into valid Gherkin .feature files, and vice versa. By maintaining structural integrity and applying pattern mapping during transformation, it ensures that acceptance criteria remain synchronized with automated test scenarios throughout the software development lifecycle, facilitating better collaboration between technical and non-technical stakeholders.

Key Features

01Smart pattern mapping for translating requirement constraints into Given/When/Then steps

02Extracts inline acceptance criteria from documentation into standalone scenarios

03Bi-directional conversion between Gherkin/BDD and EARS requirements logic

04Transforms canonical markdown specifications into executable .feature files

0538 GitHub stars

06Automated format detection and Gherkin syntax validation

Use Cases

01Generating automated test scenarios from existing requirement documents or EARS syntax

02Synchronizing documentation by converting Gherkin scenarios back into readable requirements for stakeholders

03Standardizing legacy specifications into a unified BDD format for Cucumber or Behave testing frameworks

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add melodic-software/claude-code-plugins gherkin-convert

For use in Claude.ai and ChatGPT

Download Skill