cucumber-automation

Extract Gherkin scenarios from story markdown into .feature files and generate step stubs.

23|7|Updated Feb 14, 2026

Search Tags:#automation #gherkin #cucumber #step-definitions #feature-file #story-sync

Ready to run

npx skills add https://github.com/kinncj/MAPLE --skill cucumber-automation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cucumber-automation
Source: https://github.com/kinncj/MAPLE/tree/main/template/.opencode/skills/cucumber-automation
Command: npx skills add https://github.com/kinncj/MAPLE --skill cucumber-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract Gherkin scenarios from story markdown files and convert them into runnable .feature files, while generating step definition stubs for multiple test stacks, keeping the single source of truth in docs/stories synced with tests.

Core Features & Use Cases

Gherkin extraction from stories into feature files, with idempotent updates.
Feature generation that creates per-EPIC feature files under tests/features and aligns stories with the test suite.
Step stub generation for TypeScript, JavaScript, Python (behave), and Java to scaffold test implementations.

Quick Start

Use this skill to sync your docs with runnable feature files and generate ready-to-implement steps.

Frequently Asked Questions about cucumber-automation

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

FAQPage Schema

How do I extract Gherkin scenarios from markdown story files into feature files?▼

Gherkin scenario extraction parses story markdown files and converts documented scenarios into runnable .feature files under tests/features, keeping docs/stories synced with the test suite.

Can I generate step definition stubs for Python behave and Java from feature files?▼

Yes, step definition stub generation scaffolds ready-to-implement test steps for TypeScript, JavaScript, Python (behave), and Java by detecting the repository stack and writing files under tests/step-definitions.

What is the best way to keep Cucumber feature files in sync with story documentation?▼

Keeping Cucumber feature files in sync with story documentation requires automated Gherkin extraction with idempotent updates, ensuring per-EPIC feature files align with the test suite without creating duplicates.

Does this Gherkin automation tool detect the repository stack to select the right stub generator?▼

Yes, stack detection identifies the repository's programming language to select the appropriate step definition stub generator for TypeScript, JavaScript, Python (behave), or Java test scaffolding.

How do I scaffold test implementations for TypeScript and JavaScript from Gherkin stories?▼

Scaffolding test implementations for TypeScript and JavaScript involves generating step definition stubs from Gherkin stories, creating ready-to-code files under tests/step-definitions.