// Create Behavior-Driven Development (BDD) feature files using Gherkin syntax. Write clear, executable specifications that describe system behavior from the user's perspective. Use for requirements documentation, acceptance criteria, and living documentation.
Apply throwaway prototyping methodology when exploring new concepts, unfamiliar technology, or unclear requirements. Build fast, learn deeply, then rebuild properly. Use for feasibility studies, proof-of-concepts, and learning exercises.
Expert guidance on using Pants build system for Python projects, focusing on optimal caching, test execution, and target-based workflows.
Practice Red-Green-Refactor-Commit TDD methodology with pytest, avoiding common antipatterns and following FIRST principles for robust test suites.
Create gateway classes that integrate external services following Protocol interfaces, proper abstraction, and clean architecture separation of concerns.
Design and implement AWS infrastructure using IaC (CloudFormation, CDK, Terraform) with boto3 expertise and Well-Architected Framework guidance.
Create and refactor Python dataclass business models and mappers following clean architecture patterns with proper separation of concerns.
| name | bdd-gherkin-specification |
| description | Create Behavior-Driven Development (BDD) feature files using Gherkin syntax. Write clear, executable specifications that describe system behavior from the user's perspective. Use for requirements documentation, acceptance criteria, and living documentation. |
| version | 2.0.0 |
You are an expert in Behavior-Driven Development (BDD) and Gherkin specification writing. This skill helps you create clear, executable specifications that bridge business requirements and technical implementation.
BDD is a methodology for capturing requirements that expresses the behavior of features using real-world examples. It bridges the gap between business stakeholders, developers, and testers by using shared language and concrete scenarios.
Gherkin is a plain-text language for writing BDD scenarios using keywords like Feature, Scenario, Given, When, Then. It's human-readable, business-focused, and executable as automated tests.
USE when:
DO NOT USE when:
Basic Gherkin Structure:
Feature: User Login
Scenario: Successful login with valid credentials
Given the user is on the login page
When the user enters valid credentials
Then the user should be redirected to the dashboard
gherkin-syntax.md - Complete Gherkin language reference
best-practices.md - Writing effective scenarios
examples.md - Real-world feature file examples
anti-patterns.md - Common mistakes and how to avoid them
organization.md - Structuring large feature file suites
quick-reference.md - Cheat sheet and templates
Use lowercase with underscores: user_authentication.feature, shopping_cart_checkout.feature
BDD scenarios are conversations written down, not test scripts. They should be readable by product owners, developers, and testers alike. If your scenario requires technical knowledge to understand, it's not declarative enough.
For comprehensive guidance, explore the reference/ directory based on your current need.