implement-with-tdd

Enforce test-driven development workflows for software implementation and bug fixes.

30|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Codagent-AI/agent-skills --skill implement-with-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-with-tdd
Source: https://github.com/Codagent-AI/agent-skills/tree/main/skills/implement-with-tdd
Command: npx skills add https://github.com/Codagent-AI/agent-skills --skill implement-with-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the widespread issue of shipping untested, buggy production code that leads to costly post-release debugging, customer-facing outages, and accumulating technical debt by enforcing strict test-driven development (TDD) practices across all implementation work.

Core Features & Use Cases

  • Mandatory TDD Cycle Enforcement: Requires writing a failing test before any production code is written, with clear rules against keeping unverified code as "reference" or skipping tests for non-exempt tasks.
  • Test Type Selection Guidance: Helps developers choose the appropriate test level (unit, integration, end-to-end) based on the scope of the work to avoid over-engineering or insufficient test coverage.
  • Rationalization Prevention: Includes common excuse busters and a pre-completion verification checklist to ensure TDD is followed consistently, even under tight deadlines.
  • Use Case: When fixing a bug in user session handling, this Skill ensures you first write a test that reproduces the expired session issue, watch it fail, then implement minimal code to pass it, preventing the bug from reoccurring in future releases.

Quick Start

Ask the AI to implement a new password reset feature using test-driven development to validate all edge cases like expired tokens and invalid email formats before deployment.

Frequently Asked Questions about implement-with-tdd

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

FAQPage Schema
How do I enforce test-driven development when fixing bugs or refactoring code?

Test-driven development requires writing a failing test before any production code, then implementing minimal code to pass it. This eliminates untested changes and prevents recurring bugs during refactoring or bug fix tasks.

What is the best way to choose test types for new software features?

The best way to choose test types is matching the test level to the work scope. Select unit, integration, or end-to-end tests based on feature boundaries to prevent over-engineering while ensuring sufficient test coverage for reliable software.

Can I skip writing failing tests for small code refactoring tasks?

You cannot skip failing tests for refactoring tasks. Strict TDD workflows mandate tests for all implementation work to eliminate unverified production code, using excuse busters and verification checklists to ensure compliance even under tight deadlines.

Why does test-driven development help prevent bugs in production code?

Test-driven development prevents bugs by requiring a failing test that reproduces the defect before implementation. This ensures all production code is verified against expected behavior, reducing costly post-release debugging and accumulating technical debt.

When do I need to write tests before implementation for behavior changes?

You need to write tests before implementation for any behavior change request. Mandating a failing test first ensures the new behavior is explicitly defined and verified, guaranteeing full compliance with TDD principles across the codebase.