implement-feature

Implement feature code by writing production logic that satisfies the Given/When/Then steps defined in your Gherkin scenarios. After step definitions are in place and scenarios are failing, generate the actual functions and helpers in your implementation files, tag them with REQ-*/BR-* identifiers, and verify all scenarios now pass.

Step definitions map Gherkin language to test code and assertions; feature implementation writes the production code those steps invoke. Step definitions verify behavior; implementation delivers it. Both are required in the BDD workflow.

Use BDD when requirements need to be executable and testable by non-technical stakeholders, or when you want to prevent over-engineering by tying implementation directly to specified behavior. The Gherkin → step definitions → implementation cycle ensures code aligns with business needs.

No. This Skill requires existing step definitions and failing scenarios before implementation. Step definitions must be in place to define what the production code should do; without them, there's no specification to implement against.

Tag your production code with REQ-* or BR-* identifiers to map implementation back to requirements and business rules. This traceability links each code section to the behavior it satisfies, improving auditability and maintenance.

The Skill works with Gherkin feature files and supports any language with BDD frameworks—Python, JavaScript, Java, and others. Implementation depends on your test framework (Cucumber, Behave, etc.) and production codebase structure.