test-driven-development

Enforce test-first development with failing tests before production code.

Updated May 24, 2026
One-click install
npx skills add https://github.com/anxiety135790/hermes-skills --skill test-driven-development-anxiety135790
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/anxiety135790/hermes-skills/tree/main/software-development/test-driven-development
Command: npx skills add https://github.com/anxiety135790/hermes-skills --skill test-driven-development-anxiety135790

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid fragile code by enforcing a strict test-first workflow, so features and fixes are validated before implementation begins.

Core Features & Use Cases

  • RED-GREEN-REFACTOR discipline: Write a failing test first, implement the smallest change to pass, then clean up safely.
  • Bug fix verification: Reproduce defects with tests so every fix is proven and protected against regressions.
  • Development guardrails: Apply TDD to new features, refactors, and behavior changes with clear checks for failure, pass, and full-suite validation.
  • Use case: When adding a retry mechanism, you first write a test that proves the third attempt succeeds, then implement only enough code to make that test pass.

Quick Start

Ask the agent to implement your change using strict test-driven development and verify each step from failing test to full test pass.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I enforce test-driven development for new features and bug fixes?▼

Test-driven development is enforced by requiring a failing test before any production code, validating each step of the RED-GREEN-REFACTOR cycle for features, bug fixes, and behavior changes.

What's the best way to reproduce a defect with unit tests before fixing it?▼

Reproducing defects with unit tests involves writing a failing test that proves the defect, implementing the smallest code change to make it pass, and running a full-suite verification for regression protection.

How does the RED-GREEN-REFACTOR cycle work when writing unit tests?▼

The RED-GREEN-REFACTOR cycle works by first writing a failing test, implementing the minimal change to pass the test, and then cleaning up the code safely while maintaining behavior-focused coverage.

Can I use TDD for refactoring existing code without breaking behavior?▼

TDD can be used for refactoring by applying development guardrails that verify full test suite passes before and after changes, ensuring behavior changes are validated deterministically.

When do I need full-suite verification during test-first development?▼

Full-suite verification is needed during test-first development after implementing minimal changes to pass a failing test, ensuring deterministic verification and regression protection across the software project.

Why write a failing test first before implementing production code?▼

Writing a failing test first avoids fragile code by enforcing a strict test-first workflow, ensuring features and fixes are validated with clear test design before implementation begins.