bdd-gherkin-lifecycle

Define authoring, implementation, and validation protocols for BDD Gherkin scenarios.

Updated Mar 20, 2026

Search Tags:#workflow #validation #bdd #gherkin #acceptance-criteria #test-design #uat

Ready to run

npx skills add https://github.com/jfriisj/coding-agents --skill bdd-gherkin-lifecycle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bdd-gherkin-lifecycle
Source: https://github.com/jfriisj/coding-agents/tree/main/context-ligt-workflow/skills/bdd-gherkin-lifecycle
Command: npx skills add https://github.com/jfriisj/coding-agents --skill bdd-gherkin-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BDD Gherkin lifecycle protocols ensure clear, testable requirements bridging business intent and implementation. It standardizes how Gherkin scenarios are authored, implemented, and validated across the agentic pipeline.

Core Features & Use Cases

Authoring guidelines: One Scenario per AC, Declarative, not Imperative, Strict Syntax.
Implementation & Test Strategy: When QA designs tests or Implementers write tests, copy the exact Gherkin text into the test function docstring or as inline comments; ensure the test function name references the AC number; provide a Python example illustrating the mapping.
Validation & Reporting: Ensure a strict BDD Traceability Matrix is produced (e.g., in agent-output/qa/) and aligns with UAT handoff.

Quick Start

Follow these protocols to author, implement, and validate BDD Gherkin scenarios in your project.

Frequently Asked Questions about bdd-gherkin-lifecycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write BDD Gherkin scenarios that map cleanly to acceptance criteria?▼

To write BDD Gherkin scenarios that map cleanly to acceptance criteria, author one scenario per AC using declarative, strict syntax. This ensures clear, testable requirements that bridge business intent and implementation.

What is the best way to link Gherkin test functions to acceptance criteria?▼

The best way to link Gherkin test functions to acceptance criteria is copying the exact Gherkin text into the test function docstring or inline comments, and ensuring the test function name directly references the AC number.

How do I maintain BDD traceability from Epic mapping to UAT handoff?▼

Maintain BDD traceability from Epic mapping to UAT handoff by producing a strict BDD Traceability Matrix in your QA output directory. This standardizes validation and reporting across the entire lifecycle.

When should I use declarative Gherkin syntax instead of imperative steps?▼

Use declarative Gherkin syntax instead of imperative steps when defining acceptance criteria to focus on business intent rather than UI interactions. This prevents brittle tests and ensures standardized workflow across product teams.

Does this BDD validation workflow support QA test design and developer implementation?▼

This BDD validation workflow supports both QA test design and developer implementation by providing unified handoff protocols. It standardizes how Gherkin scenarios are authored, implemented, and validated across the agentic pipeline.