test-driven-development

Enforce the Red-Green-Refactor cycle with automated tests via terminal.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common issue of brittle, untested code by enforcing a strict Test-Driven Development (TDD) workflow that ensures every line of production code is verified by a failing test first.

Core Features & Use Cases

  • Red-Green-Refactor Enforcement: Guides the agent through the mandatory cycle of writing a failing test, implementing minimal code, and refactoring.
  • Regression Prevention: Ensures that all new features and bug fixes are backed by automated tests, preventing future regressions.
  • Use Case: When implementing a complex feature, the agent uses this skill to write a specific test case that fails, then writes only the code necessary to pass that test, ensuring high code quality and test coverage.

Quick Start

Use the test-driven-development skill to guide the implementation of the new user authentication module by writing the failing test first.

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 strict test-driven development when implementing new features?

Test-driven development enforces the Red-Green-Refactor cycle to ensure all production code is verified by automated tests. It guides you to write a failing test first, implement minimal passing code, then refactor to prevent regressions.

What is the Red-Green-Refactor cycle in software testing?

The Red-Green-Refactor cycle is a test-driven development workflow requiring a failing test, minimal code implementation to pass it, and subsequent refactoring. This ensures every line of production code is verified by an automated test first.

How do I write failing tests before implementing production code?

You write failing tests first by defining specific test cases that verify code behavior against requirements. The test-driven development workflow then guides you to implement only the minimal production code necessary to make those failing tests pass.

Do I need terminal access to execute automated test suites for TDD?

Yes, terminal access is required to execute automated test suites and verify code behavior against requirements. The test-driven development workflow relies on running tests to confirm the Red-Green-Refactor cycle at each step.

Can I use test-driven development for bug fixing and system refactoring?

Yes, test-driven development applies to bug fixing and system refactoring, not just feature implementation. It ensures all bug fixes are backed by automated tests, preventing future regressions while improving code quality.

Why should I write a failing test before writing the code to pass it?

Writing a failing test first ensures that every line of production code is verified by automated tests, preventing brittle untested code. It enforces the Red-Green-Refactor cycle to guarantee high test coverage and robust code.