skills.rest
jarredkenny
jarredkennyCOMMUNITY
Explore all skills by this author →
Website𝕏@jarredkennyGitHub

test-driven-development

Guide test creation, minimal code, and refactoring through a red-green-refactor cycle.

19|4|Updated Feb 1, 2026
Search Tags:#workflow#testing#TDD#test-driven development#red-green-refactor#software-engineering
One-click install
npx skills add https://github.com/jarredkenny/agency-ai --skill test-driven-development-jarredkenny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/jarredkenny/agency-ai/tree/main/roles/orchestrator/skills/test-driven-development
Command: npx skills add https://github.com/jarredkenny/agency-ai --skill test-driven-development-jarredkenny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development (TDD) guides teams to write tests before production code, ensuring verifiable behavior and safer refactors, reducing debugging time.

Core Features & Use Cases

  • Test-first workflow: Write a failing test, implement minimal code, then refactor with confidence.
  • Risk reduction: Early detection of design flaws and regressions across features.
  • Use Case: When adding a new feature, you create a failing test first, implement code to satisfy it, and continuously verify with tests.

Quick Start

To begin TDD: write a failing test for the desired behavior, implement the minimal code to pass it, and iterate until all tests 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 is a workflow where you write a failing test first, implement minimal production code to pass it, and then refactor. This red-green-refactor cycle ensures verifiable behavior and safer code changes.

How do I start writing tests before production code for a new feature?▼

To start test-driven development for a new feature, write a failing test for the desired behavior, implement the minimal code required to satisfy that test, and iterate until all tests pass.

Why does writing tests first reduce debugging time during refactoring?▼

Writing tests first reduces debugging time by providing early detection of design flaws and regressions. You refactor with confidence because the existing tests continuously verify the software's expected behavior.

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

Yes, test-driven development applies to bug fixes and refactoring by guiding test creation for the expected fix, writing minimal code to pass, and verifying the refactor does not introduce regressions.

What are the limitations of using a test-first workflow for software engineering?▼

A test-first workflow requires strictly enforcing the red-green-refactor cycle, which may slow down initial feature delivery. It demands writing a failing test before any production code, impacting rapid prototyping speed.

Related Skills

Explore More Software Engineering Skills→
ed3daied3dai
5

test-driven-development

Guide developers through the red-green-refactor cycle with failing tests before implementation.

Official
Intermediate
SOLEROMSOLEROM

tdd-workflow

Enforce test-driven development with tests before code and 80%+ coverage validation.

Community
Intermediate
zero3041zero3041
1

gitnexus-refactoring

Analyze and manage code change impact with gitnexus for safe refactoring.

Community
Advanced
bradygasterbradygaster
3.1k

My Skill

Test trigger and role assignment mechanisms with Vitest.

Community
Basic