v1.0.2 - 2026-07-15

Fixed

• speckit.bdd.scenarios and speckit.bdd.verify now resolve the active feature's spec.md via SPECIFY_FEATURE_DIRECTORY or .specify/feature.json, matching how current Spec Kit actually writes specs (<feature-directory>/spec.md, e.g. specs/003-user-auth/spec.md). Previously both commands only looked for .specify/specify.md or root specify.md, which Spec Kit never creates, so both commands always reported "No specification found" in a standard project. The old paths remain as a last-resort fallback.

v1.0.1 — BDD/ATDD Extension for Spec-Kit

spec-kit-bdd v1.0.1

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