tdd-process

Enforces a strict TDD workflow via a multi-state governance model.

334|43|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/NTCoding/claude-skillz --skill tdd-process-ntcoding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-process
Source: https://github.com/NTCoding/claude-skillz/tree/main/tdd-process
Command: npx skills add https://github.com/NTCoding/claude-skillz --skill tdd-process-ntcoding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a disciplined Test-Driven Development workflow by controlling state transitions, ensuring failing tests are meaningfully used to drive minimal implementations, and mandating end-to-end verification before completion.

Core Features & Use Cases

  • State machine governance for PLANNING, RED, GREEN, REFACTOR, VERIFY, BLOCKED, and VIOLATION_DETECTED to guide TDD cycles.
  • Automated post-conditions checks, mandatory state announcements, and evidence-based progress to prevent silent progress.
  • Use when teams want strict TDD discipline in software development tasks, code reviews, or coaching sessions to ensure test-driven practices are followed.

Quick Start

To start a TDD-driven cycle, enable the tdd-process skill in your prompts and trigger a test-first workflow.

Frequently Asked Questions about tdd-process

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

FAQPage Schema
How do I enforce strict test-driven development during feature development?

A state-machine governance model enforces strict TDD discipline by controlling transitions through PLANNING, RED, GREEN, REFACTOR, and VERIFY states with mandatory announcements. This prevents silent progress and ensures meaningful test-driven cycles.

What is the red-green-refactor cycle in software engineering?

The red-green-refactor cycle is a TDD workflow where you write a failing test, implement minimal code to pass it, and then refactor. A strict state-machine governance model enforces these phases sequentially with automated post-condition checks and evidence-based progress.

Can I use this TDD governance model for coaching and educational contexts?

Yes, you can use this TDD governance model for coaching and educational contexts. It applies to software development tasks, code reviews, and coaching sessions where demonstrable test-driven discipline and strict workflow enforcement are required.

How do I prevent silent progress during code refactoring?

You prevent silent progress during code refactoring by using a state machine that mandates evidence-based progress and automated post-condition checks. It requires explicit state announcements before transitioning between RED, GREEN, and REFACTOR phases.

Does strict TDD require lint and build checks before completion?

Yes, strict TDD requires lint and build checks before completion. The workflow mandates end-to-end verification in the VERIFY state, ensuring full functional validation, minimal implementations, and successful builds before a feature is considered complete.

Why does my TDD workflow need a BLOCKED or VIOLATION_DETECTED state?

A TDD workflow needs BLOCKED and VIOLATION_DETECTED states to handle strict governance exceptions. These states capture scenarios where progress is impeded or test-driven discipline is broken, ensuring the cycle pauses for resolution rather than failing silently.