tdd-workflow

Enforce Test-Driven Development with 80%+ coverage across unit, integration, and E2E tests.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/koumatsumoto/.claude --skill tdd-workflow-koumatsumoto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/koumatsumoto/.claude/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/koumatsumoto/.claude --skill tdd-workflow-koumatsumoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures every development task follows Test-Driven Development with sufficient test coverage, preventing regressions and guiding robust design.

Core Features & Use Cases

  • TDD-first workflow for new features, bug fixes, and refactors
  • Enforces 80%+ test coverage across unit, integration, and E2E tests
  • Step-by-step workflow from writing tests to refactoring with green tests

Quick Start

Write the initial tests to define expected behavior, then implement the minimal code to pass, and iterate toward green tests with 80%+ overall coverage.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce a test-driven development workflow with 80% test coverage?

To enforce test-driven development, you write initial tests first, implement minimal code to pass, and iterate until achieving 80%+ overall coverage across unit, integration, and E2E tests. This workflow prevents regressions and guides robust design.

What is the best way to structure TDD for feature development and refactoring?

The best way to structure TDD involves a step-by-step workflow: write tests to define expected behavior, implement code to pass, verify coverage, and refactor while keeping tests green. This applies to feature development, bug fixes, and refactors.

Can I use Playwright E2E tests within a test-driven development process?

Yes, test-driven development patterns include Playwright E2E tests. The workflow supports writing API and E2E tests first, implementing code to pass them, and verifying comprehensive regression safety nets across all test layers.

How does writing tests first improve regression safety during bug fixes?

Writing tests first improves regression safety by defining expected behavior before implementation. This TDD workflow ensures every bug fix has a comprehensive safety net, preventing future regressions and maintaining 80%+ code coverage.

Does test-driven development require unit, integration, and E2E tests to pass before refactoring?

Yes, test-driven development requires keeping unit, integration, and E2E tests green before and during refactoring. This ensures reliable, maintainable code and a comprehensive regression safety net throughout the entire workflow.