[Extension]: Update BDD to v1.0.3 and rename it in the catalog

[RSginer]

Extension ID

bdd

Extension Name

BDD

Version

1.0.3

Description

Convert specs to Gherkin scenarios, scaffold step definitions, and verify acceptance test coverage.

Author

RSginer

Repository URL

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

Download URL

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

License

MIT

Homepage (optional)

https://rsginer.github.io/spec-kit-bdd/

Documentation URL (optional)

https://rsginer.github.io/spec-kit-bdd/

Changelog URL (optional)

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

Required Spec Kit Version

=0.2.0

Required Tools (optional)

- pytest-bdd - optional
- behave - optional
- @cucumber/cucumber - optional
- cucumber - optional
- io.cucumber - optional
- SpecFlow - optional

Number of Commands

3

Number of Hooks (optional)

2

Tags

bdd, gherkin, atdd, acceptance-testing, tdd

Key Features

• Automatic spec-to-scenario traceability generated from specifications
• Acceptance tests created before implementation starts
• Minimal setup footprint (YAML manifest + Markdown prompts only)
• Automated coverage gap detection
• Native integration with spec-kit lifecycle hooks (after_specify, before_implement)
• Multi-language step definition scaffolding (Python, JS, Ruby, Java, C#)
• New in 1.0.3: speckit.bdd.scenarios detects the project's consumer type (REST API, GraphQL, CLI, library/SDK, human UI) and reframes generated Gherkin into that actor's phrasing instead of copying the spec's generic wording verbatim

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

https://github.com/RSginer/spec-kit-bdd/tree/main/examples

Example Usage

specify extension add bdd --from https://github.com/RSginer/spec-kit-bdd/archive/refs/tags/v1.0.3.zip

/speckit.bdd.scenarios
/speckit.bdd.scaffold
/speckit.bdd.verify

Proposed Catalog Entry

{
  "bdd": {
    "name": "BDD",
    "id": "bdd",
    "description": "Convert specs to Gherkin scenarios, scaffold step definitions, and verify acceptance test coverage.",
    "author": "RSginer",
    "version": "1.0.3",
    "download_url": "https://github.com/RSginer/spec-kit-bdd/archive/refs/tags/v1.0.3.zip",
    "repository": "https://github.com/RSginer/spec-kit-bdd",
    "homepage": "https://rsginer.github.io/spec-kit-bdd/",
    "documentation": "https://rsginer.github.io/spec-kit-bdd/",
    "changelog": "https://github.com/RSginer/spec-kit-bdd/releases",
    "license": "MIT",
    "category": "process",
    "effect": "read-write",
    "requires": {
      "speckit_version": ">=0.2.0",
      "tools": [
        {
          "name": "pytest-bdd",
          "required": false
        },
        {
          "name": "behave",
          "required": false
        },
        {
          "name": "@cucumber/cucumber",
          "required": false
        },
        {
          "name": "cucumber",
          "required": false
        },
        {
          "name": "io.cucumber",
          "required": false
        },
        {
          "name": "SpecFlow",
          "required": false
        }
      ]
    },
    "provides": {
      "commands": 3,
      "hooks": 2
    },
    "tags": [
      "bdd",
      "gherkin",
      "atdd",
      "acceptance-testing",
      "tdd"
    ],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-07-15T00:00:00Z",
    "updated_at": "2026-08-21T00:00:00Z"
  }
}

Additional Context

This is a version-bump update (1.0.2 -> 1.0.3) for an extension already listed in the community catalog. Originally submitted as PR #4245 (#4245), which was closed by a maintainer asking that extension updates go through this issue template instead so the automated catalog validation pipeline can run. Full changelog: https://github.com/RSginer/spec-kit-bdd/blob/main/CHANGELOG.md#103---2026-08-21

[RSginer]

#4245

[github-actions]

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

[github-actions]

Pull request created: #4299

Generated by Add Community Extension from Issue Submission · 204.9 AIC · ⌖ 16.4 AIC · ⊞ 35.3K

[KSchlobohm]

Hi @RSginer — Copilot found an issue in PR #4299 that blocks review:

Renaming this entry changes its sort key, so leaving it between “Spec Validate” and “Spec2Cloud” breaks the community table’s required alphabetical ordering. Move the BDD row to the B section before Blueprint (the catalog workflow requires rows to be alphabetical by extension name; see .github/skills/add-community-extension/SKILL.md:111,168).
#4299 (comment)

Reply here when fixed so we can re-check the PR.

[RSginer]

done here: #4308