skills.rest
Plaidmustache
PlaidmustacheCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce a test-first workflow requiring a failing test before production code.

Updated May 4, 2026
Search Tags:#testing#tdd#quality#red-green-refactor#software-engineering#test-driven-development
One-click install
npx skills add https://github.com/Plaidmustache/hermes-nulab --skill test-driven-development-plaidmustache
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/Plaidmustache/hermes-nulab/tree/main/skills/software-development/test-driven-development
Command: npx skills add https://github.com/Plaidmustache/hermes-nulab --skill test-driven-development-plaidmustache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a test-first workflow by requiring a failing test before writing production code.

Core Features & Use Cases

  • Enforces RED-GREEN-REFACTOR cycle as a development discipline.
  • Guides on when to apply TDD (new features, bug fixes, refactoring, behavior changes).
  • Provides recommendations for writing effective tests and avoiding mocks where possible.
  • Example: When adding a feature, you first write a failing test, then implement minimal production code to pass it, then refactor for readability and maintainability.

Quick Start

Start by writing a failing test for the feature you plan to implement, then write minimal production 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
What is the test-driven development workflow for writing new features?▼

Test-driven development enforces a RED-GREEN-REFACTOR cycle where you write a failing test first, implement minimal production code to pass it, then refactor for readability and maintainable code.

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

Start test-first development by writing a descriptive, minimal failing test for your planned feature, then write just enough production code to make it pass before refactoring.

When should I apply test-driven development for bug fixes and refactoring?▼

Apply test-driven development during new feature creation, bug fixes, refactoring, and behavior changes to enforce discipline and ensure maintainable code across any project size.

Does test-driven development work with pytest and common testing tooling?▼

Yes, test-driven development specifies a minimal, descriptive test approach that is executable via common tooling like pytest, guiding teams across languages and project sizes.

What are the guardrails to prevent skipping tests during test-first development?▼

Test-first development guardrails prevent skipping tests and avoid premature optimization by enforcing the RED-GREEN-REFACTOR cycle, recommending effective tests over mocks where possible.

Related Skills

Explore More Software Engineering Skills→
icyzhicyzh
1

test-driven-development

Enforce Test-Driven Development by creating failing tests before production code.

Community
Advanced
parcadeiparcadei
3.9k

test-driven-development

Enforce test-first development using Red-Green-Refactor with failing tests before production code.

Community
Basic
YunosukeYoshinoYunosukeYoshino

tdd-workflow

Enforce red-green-refactor loops and prevent skipped tests in unit test workflows.

Community
Intermediate
AlabamaMikeAlabamaMike

test-driven-development

Enforce failing tests before production code across software projects.

Community
Basic