atdd

Drives feature development through acceptance test driven development with Gherkin specs and dual test streams.

150|10|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/swingerman/engineer --skill atdd-swingerman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: atdd
Source: https://github.com/swingerman/engineer/tree/main/skills/atdd
Command: npx skills add https://github.com/swingerman/engineer --skill atdd-swingerman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often write code before agreeing on observable behavior, leading to misaligned features, untestable specs, and implementation details leaking into requirements. This Skill enforces a disciplined Acceptance Test Driven Development workflow where Given/When/Then specs come before code, and both acceptance and unit test streams must pass. ## Core Features & Use Cases - Gherkin Spec Authoring: Guides writing standard Gherkin spec.md files in pure domain language, with strict rules preventing implementation leakage (no class names, endpoints, or database references). - Test Pipeline Generation: Parses specs into a JSON IR via dae_gherkin.py and invokes a pipeline-builder agent to generate executable acceptance tests for frameworks like pytest, Jest, JUnit, Go testing, or RSpec. - Red-Green TDD Loop: Runs acceptance tests to confirm they fail, then drives implementation with unit tests until both streams pass, with optional impact analysis for faster iteration. - Use Case: When asked to build a new feature, the Skill walks through clarifying questions, co-authors approved Gherkin scenarios, generates a runnable test pipeline, and implements the feature via TDD until all scenarios pass. ## Quick Start Ask the AI to build a feature using ATDD, for example: use ATDD to implement user registration with acceptance specs first.

Frequently Asked Questions about atdd

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

FAQPage Schema
How do I write acceptance tests before code with ATDD?▼

Write a spec.md file in standard Gherkin with Feature, Scenario, Given, When, and Then steps describing observable behavior in domain language. Get user approval on the specs, then generate and run the acceptance tests to confirm they fail before implementing.

What is the difference between acceptance tests and unit tests in ATDD?▼

Acceptance tests define what the system does through external observables, while unit tests define how it does it through internal structure. Both streams must pass; neither alone is sufficient to constrain development correctly.

Which test frameworks does the ATDD pipeline support?▼

The pipeline-builder agent generates executable tests for the project's framework, including pytest, Jest, JUnit, Go testing, and RSpec. The Gherkin parser dae_gherkin.py is portable and shipped with the plugin.

Why must Gherkin specs avoid implementation details?▼

Specs must describe external observables only, never class names, API endpoints, database tables, or framework terms. This keeps specs as stable behavior contracts while the generator maps domain language to system internals.

What happens if acceptance tests pass before implementation?▼

Passing tests at the red stage mean either the behavior already exists, making the specs redundant, or the generator is not testing the right thing. Revise the specs or fix the pipeline before proceeding.