atdd

Coordinate issue-driven ATDD workflows from discovery through automated testing and merge.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/o3-ozono/atdd-kit --skill atdd-o3-ozono
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atdd
Source: https://github.com/o3-ozono/atdd-kit/tree/main/skills/atdd
Command: npx skills add https://github.com/o3-ozono/atdd-kit --skill atdd-o3-ozono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams execute an Issue-driven, test-first workflow by enforcing discovery, planning, and automated verification from requirement to merge.

Core Features & Use Cases

  • Enforces ATDD double-loop workflow: outer acceptance tests and inner unit tests to ensure verifiability.
  • Guides state gates, continuation paths, and autopilot execution to maintain progress across issues and branches.
  • Provides guardrails for readiness, branching, and commit conventions to reduce drift.

Quick Start

Start by ensuring the issue has approved ACs and a ready-to-go label, then run the skill in --autopilot mode to begin the double-loop development flow.

Frequently Asked Questions about atdd

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

FAQPage Schema
How do I automate acceptance test-driven development workflows from requirements to merge?

To automate acceptance test-driven development workflows, you need a tool that coordinates discovery, planning, and automated testing by enforcing outer acceptance tests and inner unit tests from requirement to merge.

What is the ATDD double-loop workflow and how does it ensure software verifiability?

The ATDD double-loop workflow enforces outer acceptance tests and inner unit tests to ensure verifiability. It guides state gates, continuation paths, and autopilot execution to maintain progress across issues and branches.

How do I start issue-driven test-first development with approved acceptance criteria?

To start issue-driven test-first development, ensure the issue has approved acceptance criteria and a ready-to-go label, then run the skill in autopilot mode to begin the double-loop development flow.

Can I resume automated testing progress across different sessions and feature branches?

Yes, you can resume automated testing progress across different sessions and feature branches. The workflow supports continuation paths and loads specifications from docs/specs to maintain state across execution gaps.

Does automated ATDD require approved test plans and feature branches before execution?

Yes, automated ATDD requires approved acceptance criteria, test plans, and feature branches before execution. It enforces a state-gate before execution to ensure readiness and reduce drift across issue-based projects.

What are the limitations of autopilot-guided testing for issue management?

Autopilot-guided testing for issue management is limited to issue-based projects with approved acceptance criteria and a ready-to-go label. It requires specifications in docs/specs and cannot run without passing the readiness state-gate.