full-cycle-tdd

Automate end-to-end test-driven development workflows with failing-test-first cycles.

6|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/anotherben/claude-harness --skill full-cycle-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-cycle-tdd
Source: https://github.com/anotherben/claude-harness/tree/main/skills/full-cycle-tdd
Command: npx skills add https://github.com/anotherben/claude-harness --skill full-cycle-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This solution enforces a TDD-first workflow where every task starts with a failing test and a plan, driving design quality and reducing regressions.

Core Features & Use Cases

  • Enforces failing tests before implementation to define success criteria.
  • Provides a repeatable planning-to-commit cycle with Agent Harness orchestration.
  • Ideal for bug fixes, critical features, or any work where correctness matters.

Quick Start

Invoke /full-cycle-tdd followed by a description to begin a test-driven development cycle.

Frequently Asked Questions about full-cycle-tdd

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

FAQPage Schema
How do I enforce a failing test before writing implementation code?

To enforce a failing test before implementation, this workflow mandates a test-driven development cycle where every task begins with a failing test to define success criteria and drive design quality.

What is the best way to automate a test-driven development workflow for bug fixes?

The best way to automate test-driven development for bug fixes is using an orchestrated workflow that standardizes planning, failing test generation, implementation, and staged commits to ensure high correctness.

Can I use Agent Harness for planning and review during a TDD cycle?

Yes, you can use Agent Harness for planning and review during a TDD cycle, as this workflow requires integration with Agent Harness to orchestrate the repeatable planning-to-commit cycle.

How do I standardize the workflow from planning to validation for software development?

You can standardize the workflow from planning to validation by applying a structured test-driven development process that generates plans, enforces failing tests, and executes staged commits per task.

When should I use a test-driven development workflow for my features?

You should use a test-driven development workflow for features requiring high correctness, critical bug fixes, or any software development task where reducing regressions and defining strict success criteria matter.