bdd-feature

Group functional requirements into features and generate Gherkin .feature files.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill bdd-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bdd-feature
Source: https://github.com/mahg-es/araya/tree/main/skills/bdd-feature
Command: npx skills add https://github.com/mahg-es/araya --skill bdd-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Requirements are documented but the team needs executable specifications that define behavior in a language everyone understands — business, developers, QA.

Core Features & Use Cases

  • Generate one or more Gherkin feature files from grouped functional requirements.
  • Ensure scenarios use business language and cover happy paths, edge cases, and security scenarios.
  • Output features as .feature files under features/ for seamless test integration.

Quick Start

Read specs/requirements.md and run the feature-generation workflow to produce features/*.feature files.

Frequently Asked Questions about bdd-feature

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

FAQPage Schema
How do I generate Gherkin feature files from functional requirements?

To generate Gherkin feature files from functional requirements, you group related requirements into features and output corresponding .feature files under a features/ directory, enabling automated test generation.

What is the best way to turn user stories into executable BDD specifications?

Turning user stories into executable BDD specifications involves mapping each story to a business capability and generating Gherkin scenarios that cover happy paths, edge cases, and security-related test conditions.

Can I use Gherkin feature files for QA pipeline test automation?

Yes, Gherkin feature files are designed for QA pipeline test automation. They provide business-friendly specifications written in a common language that developers, QA, and product teams can all understand and execute.

How do you cover edge cases and security scenarios in BDD specifications?

Covering edge cases and security scenarios in BDD specifications requires mapping functional requirements to business capabilities and mandating specific test scenarios that validate both normal behavior and security-related conditions.

Do I need a requirements document to create BDD feature files?

Yes, you need a requirements document, such as a specs/requirements.md file containing functional requirements, user stories, and acceptance criteria to serve as the input for generating the corresponding Gherkin feature files.