atdd

Generates executable test specifications for workflows using GanttProject's Umlet integration.

Updated Feb 17, 2026

Search Tags:#testing #bdd #gherkin #cucumber #atdd #executable specifications

Ready to run

npx skills add https://github.com/mscipio/bilt-transactions-export --skill atdd-mscipio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: atdd
Source: https://github.com/mscipio/bilt-transactions-export/tree/main/.opencode/skills/atdd
Command: npx skills add https://github.com/mscipio/bilt-transactions-export --skill atdd-mscipio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of defining and implementing software features by ensuring that acceptance criteria are clearly defined and executable before development begins, bridging the gap between business requirements and technical implementation.

Core Features & Use Cases

Gherkin Syntax Guidance: Provides clear examples and structure for writing tests using Given-When-Then.
Executable Specifications: Transforms user stories and requirements into automated tests that verify expected behavior.
Use Case: A product manager defines a new user registration flow using Gherkin scenarios. Developers then use these scenarios as a guide to build the feature, ensuring it meets the defined acceptance criteria.

Quick Start

Use the atdd skill to generate a Gherkin scenario for a successful user login.

Frequently Asked Questions about atdd

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

FAQPage Schema

How do I write executable specifications using Gherkin syntax for acceptance test driven development?▼

Executable specifications using Gherkin syntax are created by defining Given-When-Then scenarios that bridge business requirements and software implementation. This approach guides the creation of automated tests verifying expected user behavior before development begins.

What's the best way to translate user stories into automated tests using ATDD?▼

Translating user stories into automated tests through ATDD involves defining clear acceptance criteria based on user behavior. These criteria are structured as executable Gherkin scenarios, providing developers with a direct guide to build features that meet expected outcomes.

Does this ATDD approach support testing frameworks like Cucumber, Behave, and SpecFlow?▼

Yes, this ATDD approach supports automated testing frameworks like Cucumber, Behave, and SpecFlow. It bridges business requirements and technical implementation by defining executable specifications compatible with these environments.

How does acceptance test driven development bridge the gap between business requirements and implementation?▼

Acceptance test driven development bridges this gap by ensuring acceptance criteria are clearly defined and executable as Gherkin scenarios before development starts. Product managers define user behavior, and developers use these specifications to build matching features.

When do I need to use Gherkin scenarios for automated testing?▼

You need to use Gherkin scenarios for automated testing when you want to define executable specifications based on user behavior and expected outcomes. This ensures software features meet defined acceptance criteria before implementation begins.

What is the Given-When-Then structure for writing executable specifications?▼

The Given-When-Then structure is a Gherkin syntax format used for writing executable specifications. It provides clear examples and structure for defining test scenarios, bridging business requirements with software implementation in ATDD workflows.