tdd

Guide structured test-driven development workflows with RED-GREEN-REFACTOR cycles and session logs.

5|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/agentpatterns/craft --skill tdd-agentpatterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/agentpatterns/craft/tree/main/plugins/crafter/skills/tdd
Command: npx skills add https://github.com/agentpatterns/craft --skill tdd-agentpatterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Boundary-focused TDD workflow helps teams maintain strict test-first discipline, ensuring code changes are guided by tests and design intent.

Core Features & Use Cases

  • Enforces a strict RED → GREEN → REFACTOR cycle for new modules, anchored in real tests.
  • Promotes boundary testing and property-based checks via references to the boundary-testing guide.
  • Maintains a structured session log (tdd-session-log.md) and a planning/testing workflow to track progress.

Quick Start

Create tdd-session-log.md at the project root to begin a session and draft the first [TEST] plan following the ZOMBIES guidance.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I enforce a strict test-driven development workflow for new modules?

A strict test-driven development workflow is enforced by following a structured RED → GREEN → REFACTOR cycle. This Skill anchors code changes in real tests and design intent to maintain test-first discipline for new module features.

What is the best way to start a TDD session and track my testing progress?

To start a TDD session, create a tdd-session-log.md file at your project root. This artifact tracks your progress and structures your planning and testing workflow as you draft initial test plans using ZOMBIES guidance.

How does boundary testing fit into a structured TDD cycle?

Boundary testing is integrated into the TDD cycle by promoting property-based checks alongside standard tests. The workflow references a specific boundary-testing guide to ensure edge cases are evaluated during the RED and GREEN phases.

Can I use this TDD workflow for interactive, human-in-the-loop development scenarios?

Yes, this TDD workflow applies directly to interactive, human-in-the-loop scenarios. It provides explicit mode handling and structured phase guidance from planning to refactor, adapting to your interactive development process.

Do I need any specific dependencies or components to run this TDD workflow?

No specific dependencies or components are required to run this TDD workflow. You only need to create a session log file at your project root to begin enforcing the multi-phase testing and refactoring cycles.