harness-tdd

Enforce red-green-refactor cycles with Harness validation checks.

18|11|Updated Mar 16, 2026

Search Tags:#tdd #validation #red-green-refactor #ci-cd #test-driven-development #harness #software-testing

Ready to run

npx skills add https://github.com/Intense-Visions/harness-engineering --skill harness-tdd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harness-tdd
Source: https://github.com/Intense-Visions/harness-engineering/tree/main/agents/skills/claude-code/harness-tdd
Command: npx skills add https://github.com/Intense-Visions/harness-engineering --skill harness-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing reliable software often suffers from drift between tests and production code. Harness TDD enforces that no production code exists without a failing test, integrating the red-green-refactor cycle with harness validation to maintain discipline and trust in the codebase.

Core Features & Use Cases

Red-Green-Refactor workflow: A structured cycle that requires a failing test before any production code is added, followed by a green pass and refactor with safety checks.
Harness-Integrated Validation: On every change, harness checks enforce architectural boundaries, dependency constraints, and real-time feedback.
Targeted Use Cases: Ideal for feature development, bug fixes, and incremental enhancements that demand observable behavior before implementation.

Quick Start

Start the RED-GREEN-REFACTOR cycle by running the Harness TDD skill in your project to begin the validation-driven development process.

Frequently Asked Questions about harness-tdd

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

FAQPage Schema

How do I enforce a test-driven development cycle with continuous integration checks?▼

Harness validation enforces the red-green-refactor cycle by applying mandatory validation checks on every change, ensuring no production code exists without a corresponding failing test. It maintains architectural boundaries and dependency constraints during feature development and bug fixes.

What is the red-green-refactor workflow for software testing?▼

The red-green-refactor workflow is a test-first development cycle that requires writing a failing test before adding production code, followed by a passing test and a safe refactoring phase. This structured process prevents drift between tests and production code.

How to start test-driven development for feature development and bug fixes?▼

Start test-driven development by triggering the RED-GREEN-REFACTOR cycle manually, on new features, or on bug fixes. The integrated Harness validation then enforces architectural constraints and verifies observable behavior before implementation proceeds.

Does harness validation work with test-driven development for incremental enhancements?▼

Harness validation works with test-driven development for incremental enhancements by enforcing architectural boundaries and dependency constraints on every change. This targeted approach demands observable behavior before implementation across software projects.

Why use harness validation for test-first programming instead of standard testing?▼

Harness validation for test-first programming prevents drift between tests and production code by enforcing mandatory validation steps during the refactor phase. Unlike standard testing, it guarantees end-to-end quality and architectural constraint enforcement across software projects.