Converts specifications between Gherkin/BDD feature files, EARS requirements, canonical specs, and inline acceptance criteria. Useful for generating BDD tests from docs.
npx claudepluginhub melodic-software/claude-code-plugins --plugin spec-driven-developmentThis skill is limited to using the following tools:
Convert specifications between Gherkin/BDD format and other formats.
Converts specifications between EARS format and prose, Gherkin, or canonical. Parses prose to structured EARS requirements, EARS to Gherkin scenarios, and more.
Converts Lean PRDs to Gherkin .feature files with Vietnamese steps in mandatory Rule blocks. Use for generating structured BDD scenarios from product specs.
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.
Convert specifications between Gherkin/BDD format and other formats.
| From | To | Description |
|---|---|---|
| EARS | Gherkin | EARS requirements to scenarios |
| Gherkin | EARS | Scenarios to EARS requirements |
| Canonical | Gherkin | Full spec to feature file |
| Gherkin | Canonical | Feature file to canonical spec |
| Inline AC | Feature | Inline criteria to .feature |
| Feature | Inline AC | .feature to inline criteria |
Load Source
Parse Content
Convert
spec-converter gherkin agentValidate
Output
$1 - Source file path--to - Target format: gherkin, feature, canonical, ears, inline--output - Output file path (optional)# Canonical spec to feature file
/spec-driven-development:gherkin-convert .specs/auth/spec.md --to feature
# Feature file to canonical
/spec-driven-development:gherkin-convert tests/login.feature --to canonical
# EARS to Gherkin
/spec-driven-development:gherkin-convert ears-requirements.md --to gherkin
# Inline to feature file
/spec-driven-development:gherkin-convert spec.md --to feature --output tests/spec.feature
Input (EARS):
## FR-1: User Login
WHEN the user submits valid credentials,
the system SHALL authenticate the user
AND redirect to the dashboard.
### Acceptance Criteria
- AC-1.1: Valid credentials grant access
- AC-1.2: Invalid password shows error
Output (Gherkin):
Feature: User Login
As a user
I want to log in with my credentials
So that I can access the dashboard
# FR-1: User Login
Scenario: Successful login with valid credentials
Given a registered user exists
When the user submits valid credentials
Then the user is authenticated
And the user is redirected to the dashboard
Scenario: Failed login with invalid password
Given a registered user exists
When the user submits an invalid password
Then an error message is displayed
And the user remains on the login page
Input (Canonical):
# Specification: Shopping Cart
## FR-1: Add to Cart
WHEN the user clicks "Add to Cart",
the system SHALL add the item to the user's cart.
### Acceptance Criteria
- [ ] AC-1.1: Given product page, when clicking add, then item in cart
- [ ] AC-1.2: Given item in cart, when adding again, then quantity increases
Output (Feature):
# Specification: Shopping Cart
# Generated from: .specs/cart/spec.md
Feature: Shopping Cart
As a shopper
I want to add items to my cart
So that I can purchase them
@FR-1
Scenario: Add item to cart from product page
Given I am viewing a product page
When I click "Add to Cart"
Then the item is added to my cart
@FR-1
Scenario: Increase quantity when adding existing item
Given I have an item in my cart
When I add the same item again
Then the item quantity increases by 1
| EARS Pattern | Gherkin Mapping |
|---|---|
| WHEN...SHALL | Scenario with When/Then |
| WHILE...SHALL | Given (continuous state) |
| IF...THEN...SHALL | Error/edge case scenario |
| WHERE...SHALL | @tag for feature toggle |
| Ubiquitous | Background or invariant check |
/spec-driven-development:gherkin-author - Create Gherkin scenarios/spec-driven-development:ears-convert - EARS conversions/spec-driven-development:convert - General format conversion