skills.rest
rickyananda
rickyanandaCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

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

1|Updated May 18, 2026
Search Tags:#testing#tdd#refactoring#unit-testing#software-development#regression-prevention
One-click install
npx skills add https://github.com/rickyananda/hermes-skills --skill test-driven-development-rickyananda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/rickyananda/hermes-skills/tree/main/software-development/test-driven-development
Command: npx skills add https://github.com/rickyananda/hermes-skills --skill test-driven-development-rickyananda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unverified production code by enforcing a strict test-first workflow, reducing bugs, regressions, and guesswork during development.

Core Features & Use Cases

  • RED-GREEN-REFACTOR Discipline: Write a failing test first, implement the smallest possible fix, then clean up safely.
  • Behavior-Focused Verification: Validate real outcomes instead of implementation details, making tests more resilient and meaningful.
  • Use Case: Use this Skill when building new features, fixing bugs, or refactoring code so every change is covered by a test that was proven to fail before the code existed.

Quick Start

Ask for a strict TDD plan for your feature and have the assistant guide you from the first failing test through minimal implementation and final refactor.

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-first software development when building new features?▼

Test-first software development is enforced by requiring a failing test before writing any production code, following a strict RED-GREEN-REFACTOR cycle to ensure every new feature has reliable regression protection.

What is the RED-GREEN-REFACTOR cycle in unit testing?▼

The RED-GREEN-REFACTOR cycle in unit testing means writing a failing test first, implementing the smallest possible fix to make it pass, then cleaning up the code safely while verifying the full test suite.

How do I write behavior-focused tests instead of testing implementation details?▼

Behavior-focused tests validate real outcomes rather than implementation details, making your unit testing more resilient and meaningful while ensuring the software development process prevents unverified changes.

Can I use strict test-driven development for refactoring existing code?▼

Yes, test-driven development applies to refactoring by using behavior-focused tests to verify existing outcomes, ensuring you can clean up code safely without introducing regressions or unverified behavior changes.

When do I need to run a full test suite verification during TDD?▼

Full test suite verification is needed during the REFACTOR stage of test-driven development to prevent unverified changes and ensure that minimal implementations have not introduced regressions elsewhere.

Related Skills

Explore More Software Engineering Skills→
zccz14zccz14
4

aim-test-driven-development

Enforce test-first RED-GREEN-REFACTOR cycles for AIM repository work.

Community
Advanced
adityaarsharmaadityaarsharma
2

orbit-qa-regression-pack

Manage regression test suites with Playwright and CI pipelines.

Community
Advanced
theinternetitheinterneti

gitnexus-refactoring

Rename, extract, and split code modules within a Git repository.

Community
Advanced
JKhyroJKhyro

test-driven-development

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

Community
Advanced