Authors interactive Gherkin BDD scenarios guiding through Given/When/Then steps with best practices like single When actions and observable outcomes. Outputs .feature files for testing.
npx claudepluginhub melodic-software/claude-code-plugins --plugin spec-driven-developmentThis skill is limited to using the following tools:
Interactive assistant for creating Gherkin/BDD scenarios with best practices.
Authors Gherkin acceptance criteria and BDD feature files with Given/When/Then scenarios. Provides syntax reference, best practices, and Reqnroll setup for .NET projects.
Guides writing BDD scenarios in Gherkin with acceptance criteria, edge cases, tags, and organization. Use for defining behavior specs, test coverage, and requirements.
Generates Gherkin BDD .feature files from spec acceptance criteria. Produces one file per demoable unit alongside specs; optionally creates cw-testing task stubs.
Share bugs, ideas, or general feedback.
Interactive assistant for creating Gherkin/BDD scenarios with best practices.
| Keyword | Purpose | Example |
|---|---|---|
| Feature | Describes the feature | Feature: User Login |
| Scenario | Single test case | Scenario: Successful login |
| Given | Precondition/context | Given a registered user |
| When | Action/trigger | When they enter credentials |
| Then | Expected outcome | Then they are logged in |
| And | Continue previous | And a session is created |
| But | Negative continuation | But no email is sent |
| Background | Shared setup | Background: Given logged in |
| Scenario Outline | Parameterized | Examples table |
Gather Context
--interactive, guide through scenario creationFeature Identification
spec-author gherkin agentScenario Construction
Best Practices Check
Output
$ARGUMENTS - Feature description--interactive - Step-by-step guided authoring--output - Output .feature file path--format - Output format: feature (default), inline# From description
/spec-driven-development:gherkin-author "User can add items to shopping cart"
# Interactive mode
/spec-driven-development:gherkin-author --interactive
# Output to file
/spec-driven-development:gherkin-author "Login feature" --output tests/login.feature
# Inline acceptance criteria format
/spec-driven-development:gherkin-author "Password reset" --format inline
SCENARIO QUALITY CHECK
[✓] Name describes behavior (not implementation)
[✓] Given establishes necessary context only
[✓] When has exactly ONE action
[✓] Then has observable, verifiable outcomes
[✓] Uses business language, not technical jargon
[✓] Independent of other scenarios
[✓] Focused on one behavior
[✓] Can be automated
| Anti-Pattern | Example | Better |
|---|---|---|
| UI-coupled | "When I click the blue button" | "When I submit the form" |
| Imperative | "When I type 'john' in field" | "When I enter credentials" |
| Too many Ands | Given X And Y And Z... | Use Background |
| Testing code | "Then database has record" | "Then user is registered" |
| Vague Then | "Then it works" | "Then I see confirmation" |
Feature: Shopping Cart
As a shopper
I want to add items to my cart
So that I can purchase them later
Background:
Given I am logged in as a customer
And the product catalog is available
Scenario: Add single item to empty cart
Given my cart is empty
When I add "Widget" to my cart
Then my cart contains 1 item
And the cart total reflects the item price
Scenario: Add item already in cart
Given my cart contains 1 "Widget"
When I add another "Widget"
Then my cart contains 2 "Widget"
And the cart total is updated
### Acceptance Criteria
- [ ] AC-1: Given empty cart, when adding item, then cart contains 1 item
- [ ] AC-2: Given item in cart, when adding same item, then quantity increases
- [ ] AC-3: Given item in cart, when removing item, then cart is empty
/spec-driven-development:gherkin-convert - Convert between formats/spec-driven-development:ears-author - Create EARS requirements/spec-driven-development:specify - Generate full specification