gaia-atdd

Generate failing Given/When/Then ATDD test skeletons from acceptance criteria.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-atdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-atdd
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-atdd
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-atdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires resolve-config.sh, validate-gate.sh, checkpoint.sh, and includes scripts (resource) components.

What problem does it solve?

Automates generation of failing Acceptance Test-Driven Development (ATDD) artifacts from a story's acceptance criteria, accelerating TDD-style workflows.

Core Features & Use Cases

  • Convert each acceptance criterion into a precise Given/When/Then failing test skeleton.
  • Save the resulting ATDD artifact to docs/test-artifacts/atdd-{story_key}.md for traceability.
  • Load guidance from knowledge/api-testing-patterns.md to ensure standard patterns and schema validation.
  • Validate inputs (story key, presence of ACs) and enforce a strict 1:1 AC-to-test mapping to ensure traceability.

Quick Start

Provide a valid story-key (for example E28-S83) to generate the ATDD artifact for that story.

Frequently Asked Questions about gaia-atdd

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

FAQPage Schema
How do I generate ATDD test skeletons from acceptance criteria?

To generate ATDD test skeletons, provide a valid story key like E28-S83. The tool converts each acceptance criterion into a Given/When/Then failing test skeleton using a strict 1:1 AC-to-test mapping.

How does Given/When/Then test mapping work for story acceptance criteria?

Given/When/Then test mapping enforces a strict 1:1 ratio between acceptance criteria and generated tests. Each criterion is parsed and transformed into a precise failing test skeleton for traceability.

What's the best way to automate Acceptance Test-Driven Development artifact creation?

Automating ATDD artifact creation requires validating the story file and acceptance criteria first. The tool then generates red phase tests and saves them to docs/test-artifacts/atdd-{story_key}.md for full traceability.

Do I need a specific story key format to generate acceptance test artifacts?

Yes, you need a valid story key such as E28-S83. The tool validates the story key and presence of acceptance criteria before generating the ATDD artifact to ensure accurate test generation.

Why does the tool only produce failing tests in the red phase?

The tool produces tests in the red phase only to support strict TDD-style workflows. It generates failing test skeletons from acceptance criteria without implementation, ensuring developers write the minimum code to pass.

Can I use custom API testing patterns for generating acceptance tests?

Yes, the tool loads guidance from knowledge/api-testing-patterns.md. This ensures generated Given/When/Then test skeletons follow standard API testing patterns and schema validation specific to your project.