atdd

Generate failing executable tests from natural language acceptance criteria.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/javierhbr/agnostic-agent-loop --skill atdd-javierhbr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atdd
Source: https://github.com/javierhbr/agnostic-agent-loop/tree/main/.cursor/skills/atdd
Command: npx skills add https://github.com/javierhbr/agnostic-agent-loop --skill atdd-javierhbr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of converting acceptance criteria from tasks into executable tests, ensuring that features meet defined requirements before and during implementation.

Core Features & Use Cases

  • Test Generation: Writes failing tests directly from acceptance criteria.
  • Test-Driven Workflow: Ensures implementation strictly adheres to specified criteria.
  • Use Case: When a task includes "User can log in with email and password," this skill generates a test for that specific functionality, which must fail until the login feature is correctly implemented.

Quick Start

Use the atdd skill to write failing tests from the acceptance criteria of task TASK-001.

Frequently Asked Questions about atdd

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

FAQPage Schema
How do I turn natural language acceptance criteria into executable tests?

Executable tests are generated by translating natural language acceptance criteria into automated test cases using a test-driven development approach. This ensures that implementation directly addresses specified requirements before code is considered complete.

What is acceptance test-driven development and how does it verify product requirements?

Acceptance test-driven development (ATDD) is a verification process that translates task-defined acceptance criteria into failing automated tests. It ensures product requirements are strictly satisfied by requiring implementation to pass these tests before completion.

How do I automate test generation from task criteria using a TDD workflow?

Test generation is automated by parsing task-defined acceptance criteria and writing corresponding failing tests. The test-driven workflow requires these automated test cases to fail until the feature implementation correctly satisfies the specified criteria.

Does acceptance test automation work for feature tasks without external dependencies?

Acceptance test automation works without external dependencies by directly processing task-defined criteria. It generates executable test cases from natural language requirements, ensuring the verification of product features is self-contained within the development workflow.

Why write failing tests from acceptance criteria before starting implementation?

Failing tests are written from acceptance criteria to enforce a strict test-driven development workflow. This guarantees that implementation directly addresses and satisfies specified product requirements, ensuring features are verifiably complete before code is finalized.