| name | gherkin-expert |
| version | 1.0.0 |
| description | Gherkin/BDD expert for writing, reviewing, and refactoring Cucumber feature files and step definitions. |
| auto_activates | ["write feature file","write gherkin","BDD scenarios","cucumber feature","acceptance criteria as gherkin","review feature files"] |
| explicit_triggers | ["/gherkin","/amplihack:gherkin-expert"] |
| confirmation_required | false |
| skip_confirmation_if_explicit | true |
| token_budget | 3000 |
Gherkin Expert Skill
Expert guidance for writing, reviewing, and refactoring Gherkin feature files
and Cucumber step definitions following BDD best practices.
Capabilities
- Author well-structured
.feature files with proper Given/When/Then flow
- Review existing feature files for anti-patterns and readability issues
- Refactor imperative scenarios into declarative specifications
- Design step definitions with appropriate parameterization
- Organize feature files with tags, backgrounds, and scenario outlines
Usage
Activate explicitly with /gherkin or automatically when working with .feature
files, BDD scenarios, or acceptance criteria.
Style Guide
Preferred: Declarative
Scenario: Registered user logs in
Given a registered user "alice"
When the user logs in with valid credentials
Then the user should see the dashboard
Avoid: Imperative
Scenario: Login
Given I am on the login page
When I type "alice" into the username field
And I type "password123" into the password field
And I click the "Login" button
Then I should see the text "Dashboard"
Anti-Pattern Checklist
- Multiple behaviors per scenario — split into focused scenarios
- Missing assertions — every scenario needs a meaningful Then
- UI-coupled steps — describe behavior, not button clicks
- Giant Background — keep shared setup minimal
- Scenario Outline abuse — use only when examples vary by data
- Inconsistent domain language — align with ubiquitous language
Related Skills
- property-based-testing: Generalizes concrete Gherkin examples into
universally-quantified properties (invariant, round-trip, metamorphic).
Reach for it when a
Scenario Outline's example table is really trying to
express "for all inputs" rather than a handful of cases.
- tla-plus-expert: Formal design-level verification; together these form
the specification-and-verification triad.
