bdd-specification

Write executable Gherkin acceptance specifications from Three Amigos alignment sessions.

5|1|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/roanbrasil/engineer-grade-agent-skills --skill bdd-specification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bdd-specification
Source: https://github.com/roanbrasil/engineer-grade-agent-skills/tree/main/skills/bdd-specification
Command: npx skills add https://github.com/roanbrasil/engineer-grade-agent-skills --skill bdd-specification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the critical problem of misalignment between business stakeholders, developers, and testers that leads to misunderstood requirements, costly rework, and delivered features that fail to meet business needs. It provides a structured, collaborative framework to define and validate system behavior before any code is written, ensuring all parties have a shared understanding of expected outcomes.

Core Features & Use Cases

  • Three Amigos Alignment: Facilitate pre-development discovery sessions with business analysts, developers, and testers to align on feature requirements, edge cases, and acceptance criteria.
  • Executable Gherkin Specifications: Write human-readable, machine-executable acceptance criteria using standard Gherkin syntax that non-technical business stakeholders can read and validate.
  • Living Documentation: Maintain up-to-date, version-controlled system documentation that is automatically verified by passing test suites, eliminating stale requirement docs.
  • BDD/TDD Integration: Seamlessly combine acceptance-level BDD scenarios with unit-level TDD workflows to ensure end-to-end behavior correctness from specification to implementation.
  • Use Case Example: For a new e-commerce loyalty discount feature, use this Skill to run a Three Amigos session to align on discount rules, write Gherkin scenarios for edge cases like boundary order counts and stacked discount restrictions, and integrate those specs with your existing TDD workflow to guarantee the implementation matches the agreed business rules.

Quick Start

Use the bdd-specification skill to run a Three Amigos session for your new checkout feature and write aligned Gherkin acceptance scenarios that your product team can validate.

Frequently Asked Questions about bdd-specification

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

FAQPage Schema
How do I write executable Gherkin specifications for acceptance testing?

Executable Gherkin specifications are written using standard syntax that non-technical stakeholders can read and validate, forming human-readable, machine-executable acceptance criteria. This approach ensures all parties share an understanding of expected outcomes before development begins.

What is the Three Amigos session in BDD and how does it prevent misalignment?

A Three Amigos session in BDD is a pre-development discovery meeting with business analysts, developers, and testers to align on feature requirements. It prevents cross-team misalignment by establishing shared agreement on edge cases and acceptance criteria before coding starts.

How do I maintain living documentation synchronized with production code?

Living documentation is maintained by writing version-controlled Gherkin specifications that are automatically verified by passing test suites. This eliminates stale requirement docs by keeping your system documentation continuously synced with your actual production codebase.

Can I integrate BDD acceptance scenarios with my existing unit-level TDD workflow?

Yes, BDD acceptance scenarios integrate seamlessly with unit-level TDD workflows. This combination ensures end-to-end behavior correctness from specification to implementation, validating that complex business rules match the agreed acceptance criteria.

When do I need BDD specification for complex business rule implementation?

BDD specification is needed for complex business rule implementation, regulatory compliance verification, and long-lived product feature maintenance. It provides a structured framework for collaborative requirement definition to prevent costly rework.

What is the best way to align business stakeholders and developers on feature behavior?

The best way to align stakeholders and developers is using BDD to facilitate collaborative requirement definition and executable acceptance specification. This enforces a ubiquitous domain language in specifications, ensuring delivered features meet business needs.