skills.rest
woodrowpearson
woodrowpearsonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-driven-development

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

Updated Jul 14, 2025
Search Tags:#testing#tdd#red-green-refactor#quality-assurance#software-engineering#test-driven-development
One-click install
npx skills add https://github.com/woodrowpearson/mids-hero-web --skill test-driven-development-woodrowpearson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/woodrowpearson/mids-hero-web/tree/main/.claude/skills/test-driven-development
Command: npx skills add https://github.com/woodrowpearson/mids-hero-web --skill test-driven-development-woodrowpearson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a test-first workflow by requiring a failing test before any production code.

Core Features & Use Cases

  • Test-First Principle: Write failing tests before production code to define expected behavior.
  • Red-Green-Refactor Cycle: Follow the TDD loop to guide implementation and refactoring.
  • Documentation by Tests: Capture intent and requirements in executable tests.

Quick Start

Write a failing test that specifies the desired behavior, then implement the minimal code to make the test pass.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
What is test-driven development and how does the red-green-refactor cycle work?▼

Test-driven development (TDD) is a test-first workflow requiring a failing test before any production code. The red-green-refactor cycle defines expected behavior via a failing test, implements minimal code to pass, then refactors safely.

How do I write tests first when developing new software features?▼

To write tests first for feature development, write a failing test that specifies the desired behavior, then implement the minimal code required to make that test pass. This enforces the test-first principle and documents intent through executable tests.

Can I use test-driven development for bug fixes and refactoring?▼

Test-driven development is applicable to bug fixes and refactoring across typical software projects and languages. You write a failing test that captures the bug or desired refactored behavior, then implement minimal code to pass the test.

Does test-driven development require specific testing frameworks or dependencies?▼

Test-driven development requires no specific testing frameworks or dependencies. It is applicable across typical software projects and languages, enforcing a test-first workflow by requiring a failing test before any production code is written.

Why write a failing test before writing any production code?▼

Writing a failing test before production code defines expected behavior and documents intent through executable tests. This test-first principle ensures the production code is minimal, satisfies the red-green-refactor cycle, and builds confidence in the implementation.

Related Skills

Explore More Software Engineering Skills→
vneseyoungstervneseyoungster
27

test-driven-development

Write failing tests before implementing minimal code to pass them.

Community
Advanced
SkogAISkogAI
1

test-driven-development

Guide teams through Red-Green-Refactor by writing failing tests before production code.

Official
Basic
aaddrickaaddrick
5.3k

lint

Lint shell scripts with shellcheck and GitHub Actions workflows with actionlint.

Community
Basic
javierhbrjavierhbr

atdd

Generate failing executable tests from natural language acceptance criteria.

Community
Intermediate