skills.rest
Amfsa-tech
Amfsa-techOFFICIAL
Explore all skills by this author →
GitHub

tdd

Guide test-driven development through one-test-at-a-time cycles with minimal implementations.

Updated Aug 23, 2026
Search Tags:#tdd#refactor#integration-tests#test-driven-development#public-api#vertical-slices
One-click install
npx skills add https://github.com/Amfsa-tech/task-hub-backend --skill tdd-amfsa-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/Amfsa-tech/task-hub-backend/tree/main/skills/tdd
Command: npx skills add https://github.com/Amfsa-tech/task-hub-backend --skill tdd-amfsa-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD helps teams deliver robust software by validating behavior through public interfaces rather than implementation details. Tests should focus on what the system does, not how it does it.

Core Features & Use Cases

  • Vertical slicing workflow: One test leads to one minimal implementation, repeated to build features.
  • Public-interface testing: Tests exercise public APIs to withstand refactors.
  • Use Case: A team adds a new feature by writing a single tracer bullet test, then implementing just enough code to pass it.

Quick Start

Write a tracer bullet test that fails initially and implement just enough code to pass it.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I start test-driven development for a new feature?▼

Test-driven development starts by writing a single tracer bullet test that fails initially, then implementing just enough production code to pass it. This red-green-refactor cycle repeats to incrementally build the feature through vertical slices.

Why should integration tests target public APIs instead of implementation details?▼

Integration tests should target public APIs because they validate what the system does rather than how it does it. This strict separation between tests and production code ensures your tests withstand refactoring and keep the system robust.

What is the red-green-refactor cycle in test-driven development?▼

The red-green-refactor cycle is a test-driven development workflow enforcing one test at a time. You write a failing test, implement minimal code to pass it, and then refactor while keeping tests and production code strictly separated.

Can I use this test-driven development workflow for bug fixes?▼

Yes, this test-driven development workflow applies to both feature development and bug fixes. It guides you to validate observable behavior through public interfaces and minimal implementations, ensuring robust integration tests for the codebase.

Does test-driven development work with incremental design and refactoring?▼

Test-driven development works directly with incremental design by enforcing minimal implementations and one-test-at-a-time cycles. Focusing on public interfaces makes refactoring safe and easy within codebases that value observable behavior.

Related Skills

Explore More Software Engineering Skills→
vh2224vh2224
1

tdd

Drive feature implementation through test-first red-green-refactor cycles.

Community
Intermediate
TrebuchetDynamicsTrebuchetDynamics
5

tdd

Drive minimal implementation with integration-style regression tests in red-green-refactor cycles.

Official
Intermediate
TeiNamTeiNam
12

laravel-verification

Automate Laravel project verification for CI/CD pipelines.

Community
Advanced
ayehiaaayehiaa

tdd

Apply test-driven development through red-green-refactor cycles with behavior-focused integration tests.

Community
Intermediate