export-feature-file

Convert Gherkin or business rules into runnable .feature files for BDD frameworks.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Ting-s515/skills --skill export-feature-file
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: export-feature-file
Source: https://github.com/Ting-s515/skills/tree/main/export-feature-file
Command: npx skills add https://github.com/Ting-s515/skills --skill export-feature-file

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

將我提供的 Gherkin 文檔或業務邏輯自動轉換為可被測試框架執行的 .feature 檔案,實現測試即文件(Living Documentation)。

Core Features & Use Cases

  • 支援多種 BDD 框架,如 Cucumber/JVM、SpecFlow、Behave 等,轉換成跨語言可執行的 .feature 格式。
  • 自動組織與轉換場景(Scenario)與情境大綱(Scenario Outline),並保留 Given/When/Then 結構,方便即時執行。
  • 適用於用戶認證、購物車、API 互動等多種行為驅動測試的轉換與產出。

Quick Start

Paste your Gherkin text or business logic and receive a ready-to-run .feature file for your chosen BDD framework.

Frequently Asked Questions about export-feature-file

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

FAQPage Schema
How do I convert business rules into a runnable Feature file for Cucumber?

To convert business rules into a runnable Feature file, paste your Gherkin text or logic to automatically generate a structured .feature file suitable for BDD frameworks like Cucumber. This output adheres to the Given/When/Then structure for immediate testing execution.

Does this tool support generating Scenario Outline with Examples for data-driven tests?

Yes, generating Scenario Outline with Examples for data-driven tests is fully supported. The conversion process automatically organizes scenarios and retains the necessary Gherkin structure, enabling comprehensive behavior-driven testing across multiple data sets.

Can I use the generated .feature files with Behave or SpecFlow frameworks?

You can use the generated .feature files with frameworks like Behave, SpecFlow, and Cucumber/JVM. The Skill produces a cross-language compatible Gherkin format, allowing seamless integration into your chosen BDD testing environment.

What is the best way to turn Gherkin text into living documentation for automation testing?

The best way to turn Gherkin text into living documentation is by converting it into an executable .feature file. This process transforms business logic into a structured format that serves as both automated tests and readable documentation.

How do I structure Gherkin scenarios for API interactions and user authentication?

To structure Gherkin scenarios for API interactions or user authentication, provide your specific business logic. The tool formats these rules into proper Given/When/Then lines within a .feature file, ready for behavior-driven automation testing.