Skip to content
Agentmart
Submit a tool

bdd-implement

Implement Behavior-Driven Development scenarios — turn Given-When-Then scenarios into executable tests.

Skill by Kotivskyi

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/kotivskyi-bdd-implement

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Implement Behavior-Driven Development scenarios — turn Given-When-Then scenarios into executable tests. Use when writing step definitions or glue code, wiring Gherkin feature files to Cucumber/Jest/Vitest/Playwright/Cypress, implementing the steps behind a scenario via TDD, and making BDD scenarios pass. To author the scenarios first, use the `/bdd-create` skill.

Use cases: testing, writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/bdd-implement

What's inside

Skill name
bdd-implement
Description
Implement Behavior-Driven Development scenarios — turn Given-When-Then scenarios into executable tests. Use when writing step definitions or glue code, wiring Gherkin feature files to Cucumber/Jest/Vitest/Playwright/Cypress, implementing the steps behind a scenario via TDD, and making BDD scenarios pass. To author the scenarios first, use the `/bdd-create` skill.
License
MIT
Instructions
86 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# BDD: Implement Scenarios

Turn approved BDD scenarios into running tests. This skill covers the **execution** side: step definitions, framework glue, and driving each scenario from red to green with TDD.

It assumes scenarios already exist. To discover and author Given-When-Then scenarios and acceptance criteria first, use the `/bdd-create` skill.

## When to Use

- Writing step definitions / glue code for existing scenarios
- Wiring Gherkin feature files to a test runner (Cucumber, Jest/Vitest, Playwright/Cypress)
- Implementing the behavior behind a scenario via TDD
- Making BDD scenarios pass and verifying acceptance criteria are met

## Implementation Workflow

For each scenario produced by `/bdd-create`:

```
1. Write the step definitions (glue code) that map Given/When/Then to runner calls
2. Implement the steps using TDD:
   - Write the failing assertion (RED)
   - Implement the behavior (GREEN)
   - Refactor (REFACTOR)
3. Run the scenario and verify it passes
4. Repeat until every scenario passes and all acceptance criteria are met
```

Keep step definitions thin: they translate the scenario's business language into calls against the system. Push real logic into the application or shared helpers, not the steps.

## Tools Integration

**Gherkin/Cucumber:**
```bash
# Feature files in features/ directory
features/
├── authentication.feature
├── user_profile.feature
└── payment.feature
```

**Jest/Vitest:**
```javascript
describe('User Authentication', () => {
  it('should login with valid credentials', () => {
    // Given
    const user = createUser({ email: 'user@example.com', password: 'SecurePass123' });

    // When
    const result = login(user.email, 'SecurePass123');

    // Then
    expect(result.success).toBe(true);
    expect(result.redirectTo).toBe('/dashboard');
  });
});
```

**Playwright/Cypress:**
```javascript
test('User can login successfully', async ({ page }) => {
  // Given
  await page.goto('/login');

  // When
  await page.fill('[name="email"]', 'user@example.com');
  await page.fill('[name="password"]', 'SecurePass123');
  await page.click('button[type="submit"]');

  // Then
  await expect(page).toHaveURL('/dashboard');
  await expect(page.locator('.welcome')).toBeVisible();
});
```

## Verification

- Every scenario in the feature file passes
- Every item in the acceptance criteria checklist is satisfied
- Scenarios remain independent and can run in any order

## Integration Points

- **`/bdd-create`:** Source of the scenarios and acceptance criteria implemented here
- **TDD (test-driven):** Each scenario's steps are driven red → green → refactor
- **Documentation:** Passing scenarios serve as living, executable documentation

From Kotivskyi/skills, MIT.

More from Kotivskyi/skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 16, 2026 (1 month ago)
Last release
Jun 22, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Kotivskyi

Cite this page

bdd-implement skill. Agent Mart. https://agentmart.dev/skills/kotivskyi-bdd-implement (last updated 2026-10-24)