Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-jtbd-bdd-integration
Translating JTBD analysis to BDD scenarios - job story to Given-When-Then patterns, forces-based test discovery, job-map-based test discovery, and property-shaped criteria
Passed 16 of 22 test cases with the skill, and 8 of 22 without it.
and 6 more in the full report
9 fixed7 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before handing off generated BDD scenarios for the billing engine to acceptance designers, what check must be performed on the test data used in Given/When/Then steps?
| Checked | Without skill | With skill |
|---|---|---|
| The checklist requires concrete values instead of generic placeholders. | Missed | Passed |
The instructions your model reads when the skill loads.
Use when translating JTBD discoveries (job stories, forces, job map) into testable BDD scenarios. Job stories map naturally to Given-When-Then because both emphasize context (situation/given), action (motivation/when), and outcome (result/then).
Job Story:
When [situation],
I want to [motivation],
so I can [outcome].
BDD Scenario:
Given [the situation from the job story]
When [user takes action aligned with the motivation]
Then [the outcome is achieved and measurable]
Job Story: "When I receive an alert that a production service is degraded, I want to see the most likely root cause with supporting evidence, so I can begin remediation within minutes instead of hours."
Scenario: Root cause surfaced from degradation alert
Given the monitoring system has detected degraded response times on the payment service
And the degradation started 5 minutes ago
When the operator opens the incident dashboard
Then the system displays the top 3 probable root causes ranked by likelihood
And each root cause includes supporting metrics and log evidence
And the most likely root cause is displayed within 10 seconds
Scenario: Remediation guidance from identified root cause
Given the operator has identified the root cause as database connection pool exhaustion
When the operator selects the recommended remediation action
Then the system presents a runbook with step-by-step instructions
And the estimated time to remediate is displayed
And the operator can execute the first step directly from the dashboard
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.