test-driven-development

Name: test-driven-development
Availability: InStock
Author: jleechanorg

Enforce test-first workflows with red-green-refactor cycles and automated verification.

Updated Jun 28, 2026

Search Tags:#testing #tdd #quality #red-green-refactor #software-engineering #test-driven-development

Ready to run

npx skills add https://github.com/jleechanorg/hermes-agent --skill test-driven-development-jleechanorg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/jleechanorg/hermes-agent/tree/main/skills/software-development/test-driven-development
Command: npx skills add https://github.com/jleechanorg/hermes-agent --skill test-driven-development-jleechanorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD enforces a discipline where tests are written before production code, preventing untested features and regressions.

Core Features & Use Cases

Test-First Policy: Always start with a failing test to define the expected behavior.
Red-Green-Refactor Cycle: Guide development through iterative test failures, minimal implementations, and refactoring with confidence.
Automated Verification: Leverages a test suite to validate changes across features, bug fixes, and refactors.

Quick Start

Write a failing test for the desired behavior, then implement the minimum code to pass it.

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 discipline across feature development cycles?▼

Test-driven development discipline is enforced by ensuring tests are written before production code, preventing untested features and regressions. This applies across feature development cycles and refactor tasks by guiding teams through strict test-first workflows with automated verification.

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

The red-green-refactor cycle in software engineering is a test-driven development process where you write a failing test, implement the minimum code to pass it, and then refactor with confidence. This iterative cycle provides rapid feedback during software delivery.

How do I start writing failing tests before implementing production code?▼

To start writing failing tests before production code, define the expected behavior with a test that initially fails. Then implement the minimum code required to make the test pass, ensuring automated verification validates changes across features and bug fixes.

Does test-first workflow support bug fixes and refactoring tasks?▼

Yes, a test-first workflow supports bug fixes and refactoring tasks by leveraging an automated test suite to validate changes. This ensures rapid feedback and maintains code quality during iterative software delivery cycles.

Can I use automated verification without writing tests first for refactoring?▼

Automated verification without writing tests first is discouraged for refactoring. Test-driven development requires mandatory failing tests before production code changes, ensuring you refactor with confidence and prevent regressions across the software engineering lifecycle.