skills.rest
SeanChenR
SeanChenRCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce writing failing tests before production code.

Updated Aug 23, 2026
Search Tags:#tdd#red-green-refactor#code-quality#unit-testing#developer-workflow#test-driven-development
One-click install
npx skills add https://github.com/SeanChenR/maestro-agent --skill test-driven-development-seanchenr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/SeanChenR/maestro-agent/tree/main/.agents/skills/test-driven-development
Command: npx skills add https://github.com/SeanChenR/maestro-agent --skill test-driven-development-seanchenr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents uncertain, untested production code by ensuring behavior is specified and verified before implementation, catching bugs early and reducing regressions.

Core Features & Use Cases

  • Red-Green-Refactor workflow: Write a failing test, implement the minimal code to pass, then refactor while keeping tests green.
  • Verification discipline: Mandates observing failing tests, verifying failure reasons, and confirming clean passing test output.
  • Use Cases: New feature development, bug fixes, refactoring, and behavior changes where test-first specification reduces risk and documents intent.

Quick Start

Write a failing test that expresses the desired behavior, run the test to confirm it fails, implement the minimal code to make it pass, and then refactor while keeping tests green.

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 reliable code?▼

TDD prevents uncertain, untested production code by specifying intended behavior before implementation, catching bugs early and reducing regression risk during new feature development, bug fixes, and refactoring.

How do I start writing tests first when implementing new features?▼

Begin test-driven development by writing a failing test expressing the desired behavior, run it to confirm failure, implement minimal production code to pass the test, then refactor while maintaining green tests.

Can I use test-first development for fixing bugs and refactoring?▼

Yes, test-first development applies to bug fixes and refactoring by requiring you to specify and verify intended behavior through failing tests before changing production code, preventing regressions.

Why do I need to observe failing tests before writing production code?▼

Observing failing tests verifies the test checks the intended behavior and fails for the correct reasons, ensuring test-first discipline catches real bugs early rather than masking false positives.

What are the limitations of strict test-driven development?▼

Strict test-driven development requires writing failing tests first and verifying failure reasons before minimal implementation, which may slow initial development speed but ensures higher code quality and fewer regressions.

Related Skills

Explore More Software Engineering Skills→
ChiejiChieji

test-driven-development

Guide Red-Green-Refactor cycles with failing tests before implementation.

Community
Intermediate
TitoPrauseeTitoPrausee

test-driven-development

Enforce a test-first workflow with failing tests before production code.

Community
Advanced
minhquan2904minhquan2904

tdd-workflow

Define and enforce a Test-Driven Development workflow with RED-GREEN-REFACTOR phases.

Community
Advanced
kimprobablykimprobably

test-driven-development

Guide developers through Red-Green-Refactor with failing tests before production code.

Community
Intermediate