test-driven-development

Enforce red/green/refactor cycles for feature development, bug fixes, and refactors.

8|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/narumiruna/skills --skill test-driven-development-narumiruna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/narumiruna/skills/tree/main/skills/deprecated/test-driven-development
Command: npx skills add https://github.com/narumiruna/skills --skill test-driven-development-narumiruna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Non-trivial software changes are risky without a disciplined testing strategy; this guide helps teams implement test-driven development to reduce regressions and improve design.

Core Features & Use Cases

  • Establish failing tests before code to define expected behavior and guide implementation.
  • Apply red/green/refactor cycles to feature development, bug fixes, and refactors across codebases.
  • Improve maintainability and confidence by driving design decisions through executable tests.

Quick Start

Write a failing test for the intended feature, then implement the smallest code change to make it 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 workflow where you write a failing test, implement the smallest code change to make it pass, and then refactor. This red/green/refactor cycle defines behavior and guides reliable software changes.

How do I write unit tests before implementing new software features?

To write unit tests before implementation, establish a failing test that defines the intended feature's expected behavior. Apply the red/green/refactor cycle to guide your code changes until the executable specification is satisfied.

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

Yes, test-driven development is applicable to bug fixes and refactors across codebases. You establish failing tests to define expected behavior, then implement changes to make them pass, ensuring regression safety and deterministic test cycles.

Does test-driven development improve software design and maintainability?

Test-driven development improves maintainability and confidence by driving design decisions through executable tests. It enforces structured test authoring and evaluation, reducing regressions in non-trivial software changes.

When should I not use a test-driven development workflow?

Test-driven development may not suit trivial changes where deterministic test cycles or executable specifications add unnecessary overhead. It is designed for non-trivial software changes where regression safety and disciplined testing strategies are required.