tdd

Guide developers through Red-Green-Refactor Test-Driven Development cycles.

14|2|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/kennedym-ds/copilot_orchestrator --skill tdd-kennedym-ds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/kennedym-ds/copilot_orchestrator/tree/main/.github/skills/tdd
Command: npx skills add https://github.com/kennedym-ds/copilot_orchestrator --skill tdd-kennedym-ds

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD principles guide teams to write failing tests before implementing code, enabling safer refactors and better design decisions.

Core Features & Use Cases

  • Red-Green-Refactor workflow to drive incremental development.
  • Unit testing, integration testing, and the use of test doubles (mocks/stubs).
  • Coverage analysis to measure testing completeness across features.

Quick Start

Start by writing a failing unit test for a new function, then implement the minimal code to pass, and finally refactor for readability and maintainability.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I start writing unit tests before implementing code using TDD?

To start TDD, write a failing unit test for a new function, implement the minimal code required to pass, and then refactor for readability and maintainability.

What is the Red-Green-Refactor workflow for test-driven development?

The Red-Green-Refactor workflow drives incremental development: write a failing test, implement minimal viable code to pass it, then deliberately refactor to improve quality.

Can I use this TDD workflow with my existing testing framework?

Yes, this TDD workflow requires a testing framework such as Jest, Pytest, or Mocha to drive feature development, bug fixes, and refactoring cycles.

When should I use test doubles like mocks and stubs in integration testing?

Use test doubles like mocks and stubs during integration testing to isolate dependencies, maintain test health, and ensure safety while guiding incremental development cycles.

How do I measure testing completeness across features after refactoring?

Measure testing completeness across features by running coverage analysis after the refactoring phase to ensure test health and validate code quality improvements.