bdd-feature-file

Create and validate Gherkin feature files for BDD specifications.

1|Updated Jun 20, 2026

Search Tags:#automation #testing #bdd #gherkin #executable-spec #feature-file

Ready to run

npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill bdd-feature-file

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bdd-feature-file
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/bdd-feature-file
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill bdd-feature-file

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill bridges the gap between business requirements and technical implementation by enforcing Behavior-Driven Development (BDD) standards, ensuring that acceptance criteria are both readable by stakeholders and verifiable as automated tests.

Core Features & Use Cases

Executable Specifications: Transforms user stories into Gherkin feature files that serve as both documentation and test suites.
Quality Enforcement: Provides automated validation for BDD best practices, such as the Golden Triangle (happy, negative, and edge cases) and declarative step definitions.
Use Case: A product manager and developer use this skill to define a new feature's behavior in Gherkin, which is then automatically validated by the system to ensure it meets the team's definition-of-ready before any code is written.

Quick Start

Use the bdd-feature-file skill to scaffold a new feature file for the user authentication capability.

Frequently Asked Questions about bdd-feature-file

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

FAQPage Schema

How do I write executable Gherkin specs for BDD?▼

Executable Gherkin specs for BDD are created by standardizing feature file creation and validation, transforming user stories into living documentation that aligns with business requirements and automated test scenarios.

What is the best way to transition acceptance criteria into automated test scenarios?▼

Transitioning acceptance criteria into automated test scenarios is best achieved using the Three Amigos collaborative methodology, which enforces declarative step definitions and minimal example sets to synchronize living documentation with system behavior.

How does BDD feature file validation enforce quality for happy, negative, and edge cases?▼

BDD feature file validation enforces quality by applying the Golden Triangle methodology to verify happy, negative, and edge cases, ensuring declarative step definitions and executable specifications meet the team's definition-of-ready.

Can I use collaborative BDD methodology to define feature behavior before writing code?▼

Yes, collaborative BDD methodology allows product managers and developers to define feature behavior in Gherkin, which the system automatically validates against BDD best practices before any implementation code is written.

Why does my BDD feature file need declarative step definitions and minimal example sets?▼

BDD feature files need declarative step definitions and minimal example sets to maintain readable living documentation that remains synchronized with system behavior and serves as both stakeholder documentation and verifiable test suites.