[Extension]: BDD/ATDD Extension for Spec-Kit

[RSginer]

Extension ID

bdd

Extension Name

Spec-Kit BDD

Version

1.0.0

Description

spec-kit-bdd v1.0.0

Adds Behavior-Driven Development (BDD) and Acceptance Test-Driven Development (ATDD)
to the spec-kit workflow. Write acceptance tests before code — then verify every
requirement is covered before you ship.

Commands

Command	What it does
/speckit.bdd.scenarios	Converts your spec-kit specification into Gherkin .feature files (Given/When/Then)
/speckit.bdd.scaffold	Generates step definition stubs from your feature files, ready to implement
/speckit.bdd.verify	Produces a traceability matrix mapping spec requirements ↔ scenarios with coverage %

ATDD workflow

/speckit.specify
↓
/speckit.bdd.scenarios ← acceptance tests written (RED)
↓
/speckit.plan + /speckit.tasks
↓
/speckit.bdd.scaffold ← step stubs runnable before any code exists
↓
/speckit.implement ← code until tests go GREEN
↓
/speckit.bdd.verify ← confirm 100% spec coverage

Supported step definition frameworks

Python (pytest-bdd · behave) · JavaScript (@cucumber/cucumber) ·
Ruby (cucumber) · Java (io.cucumber) · C# (SpecFlow)

Lifecycle hooks

• after_specify — optionally generates Gherkin scenarios immediately after writing your spec
• before_implement — optionally scaffolds step stubs before starting implementation

Both hooks are optional and prompt for confirmation before running.

Requirements

• spec-kit >=0.2.0

Installation

git clone https://github.com/RSginer/spec-kit-bdd

specify extension add --dev path-of-clone/spec-kit-bdd/

Author

Rubén Soler

Repository URL

https://github.com/RSginer/spec-kit-bdd

Download URL

https://github.com/RSginer/spec-kit-bdd/archive/refs/tags/v1.0.0.zip

License

MIT

Homepage (optional)

https://github.com/RSginer/spec-kit-bdd

Documentation URL (optional)

https://github.com/RSginer/spec-kit-bdd/README.md

Changelog URL (optional)

No response

Required Spec Kit Version

=0.2.0

Required Tools (optional)

Number of Commands

3

Number of Hooks (optional)

2

Tags

bdd, gherkin, atdd", acceptance-testing, tdd, quality, lean software development, behaivour driven development

Key Features

• /speckit.bdd.scenarios — reads .specify/specify.md and generates features/*.feature Gherkin files with happy path, edge case, error, and Scenario Outline scenarios
• /speckit.bdd.scaffold — auto-detects project language and generates step definition stubs for Python (pytest-bdd/behave), JavaScript, Ruby, Java, and C#
• /speckit.bdd.verify — produces features/TRACEABILITY.md mapping every spec requirement to its covering scenarios with a coverage percentage and gap report
• after_specify hook — optionally triggers scenario generation immediately after /speckit.specify
• before_implement hook — optionally scaffolds step stubs before /speckit.implement, enforcing the ATDD "tests first" discipline

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Testing Details

41 automated tests (pytest) validate the extension's structure:

• 16 manifest tests: schema_version, extension ID, semver, required fields, all 3 commands registered with correct naming pattern, both hooks present with optional:true, hook commands reference registered commands, tags present
• 25 command content tests: each command file has valid frontmatter, references the correct spec-kit artifacts (.specify/), uses the expected output directories, mentions required concepts (Gherkin keywords, language detection, traceability matrix, coverage %)
  Tested on macOS with spec-kit >=0.2.0.

Manually tested on a typescript cucumber project.

Example Usage

Example Usage


git clone https://github.com/RSginer/spec-kit-bdd

specify extension add --dev path-of-clone/spec-kit-bdd/


# 1. After writing your spec, generate Gherkin scenarios
/speckit.bdd.scenarios

# 2. Before implementing, scaffold step stubs
/speckit.bdd.scaffold

# 3. After implementing, verify coverage
/speckit.bdd.verify

Proposed Catalog Entry

{
  "spec-kit-bdd": {
  "id": "bdd",
  "name": "Spec-Kit BDD",
  "description": "ATDD/BDD extension: convert specs to Gherkin scenarios, scaffold step definitions, and verify acceptance test coverage.",
  "author": "RSginer",
  "version": "1.0.0",
  "repository": "https://github.com/RSginer/spec-kit-bdd",
  "homepage": "https://github.com/RSginer/spec-kit-bdd",
  "documentation": "https://github.com/RSginer/spec-kit-bdd/blob/main/README.md",
  "changelog": "https://github.com/RSginer/spec-kit-bdd/blob/main/CHANGELOG.md",
  "license": "MIT",
  "download_url": "https://github.com/RSginer/spec-kit-bdd/releases/download/v1.0.0/spec-kit-bdd-1.0.0.tar.gz",
  "requires": {
    "speckit_version": ">=0.2.0"
  },
  "provides": {
    "commands": 3,
    "hooks": 2
  },
  "tags": ["bdd", "gherkin", "atdd", "acceptance-testing", "tdd", "quality"]
}
}

Additional Context

No response

[github-actions]

cc @github/spec-kit-maintainers — new catalog submission for review.

[github-actions]

Pull request created: #3518

Generated by Add Community Extension from Issue Submission · 221.4 AIC · ⌖ 14.8 AIC · ⊞ 32.9K

[mnriem]

Can you please address #3518 (review) as it appears it is not in the required extension format?