tdd

Orchestrate an adaptive TDD cycle through RED, DOMAIN, GREEN, and COMMIT phases.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/jwilger/eventcore --skill tdd-jwilger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/jwilger/eventcore/tree/main/.agents/skills/tdd
Command: npx skills add https://github.com/jwilger/eventcore --skill tdd-jwilger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the Test-Driven Development (TDD) cycle, ensuring code is built with verifiable evidence and preventing common pitfalls like skipped reviews or untested complexity.

Core Features & Use Cases

  • Adaptive TDD Cycle: Implements a five-step RED -> DOMAIN -> GREEN -> DOMAIN -> COMMIT cycle that adapts to available harness capabilities.
  • Guided vs. Automated Modes: Offers manual phase control for experienced users or full orchestration for automated execution.
  • Use Case: When developing a new feature, invoke /tdd to have the AI automatically write a failing test, define necessary types, implement the code, review for domain integrity, and commit the changes, ensuring a robust and well-tested outcome.

Quick Start

Invoke the tdd skill with /tdd to start the automated test-driven development cycle.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I automate the test-driven development cycle with an AI agent?

Automating the test-driven development cycle involves orchestrating an AI agent through RED, DOMAIN, GREEN, DOMAIN, and COMMIT phases. This Skill detects harness capabilities to route between guided manual control and automated orchestration, ensuring code quality through verifiable evidence.

What is the RED GREEN workflow in test-driven development?

The RED GREEN workflow in test-driven development is expanded here into a five-step cycle: RED, DOMAIN, GREEN, DOMAIN, and COMMIT. This adaptive process guides AI agents to write failing tests, define types, implement code, review domain integrity, and commit changes.

How do I prevent skipped tests and untested complexity during AI code generation?

To prevent skipped tests and untested complexity during AI code generation, use an automated TDD cycle that enforces verifiable evidence at each phase. This prevents common development pitfalls by requiring failing tests and domain reviews before implementation and commits.

Can I manually control TDD phases instead of fully automating the development workflow?

Yes, you can manually control TDD phases using the guided mode. The Skill detects your harness capabilities and routes between guided mode for manual phase control and automated mode for fully orchestrated execution, adapting to your preferred development workflow.

Does this TDD cycle require any specific testing frameworks or dependencies?

No specific testing frameworks or dependencies are required. The Skill operates with no dependencies and detects available harness capabilities dynamically, allowing it to adapt its test-driven development orchestration to your existing environment.

When should I use an automated TDD cycle instead of manual coding?

Use an automated TDD cycle when developing new features that require robust, well-tested outcomes. It is particularly effective when you want to ensure verifiable evidence and prevent common development pitfalls like skipped reviews or untested complexity in your codebase.