tdd-workflow

Enforce test-driven development workflows with 80% coverage across unit, integration, and E2E tests.

1.8k|303|Updated Jan 27, 2026

Search Tags:#workflow #testing #TDD #quality #E2E #integration-test #unit-test

Ready to run

npx skills add https://github.com/xu-xiang/everything-claude-code-zh --skill tdd-workflow-xu-xiang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/xu-xiang/everything-claude-code-zh/tree/main/docs/zh-TW/skills/tdd-workflow
Command: npx skills add https://github.com/xu-xiang/everything-claude-code-zh --skill tdd-workflow-xu-xiang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams instill test-driven development (TDD) principles into daily work, increasing code quality and maintainability by ensuring changes are backed by tests.

Core Features & Use Cases

Enforce TDD: Prioritize writing tests before implementing new features, fixes, or refactors.
Coverage & Quality Gates: Require unit, integration, and end-to-end tests that meet a minimum combined coverage target (e.g., 80%) and cover edge cases.
Workflow Guidance: Provide end-to-end guidance from user story to test creation, implementation, validation, and refactor.

Quick Start

Describe a feature to receive a TDD plan, including the necessary test kinds, coverage targets, and a sample test skeleton.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema

How do I enforce test-driven development practices for new features and refactoring?▼

To enforce test-driven development, you can apply a structured workflow that prioritizes writing tests before implementing new features, fixes, or refactors, ensuring code changes are always backed by tests.

What is the minimum test coverage required for a TDD workflow?▼

The minimum combined test coverage required for the TDD workflow is 80%, encompassing unit, integration, and end-to-end tests to ensure comprehensive validation and edge case coverage.

How do I write a TDD plan that includes unit, integration, and E2E tests?▼

You can generate a TDD plan by describing a feature, which provides the necessary test kinds, coverage targets, and a sample test skeleton to guide you from test creation through implementation and validation.

Can I use this TDD workflow for bug fixes as well as new feature development?▼

Yes, the TDD workflow applies to bug fixes, new feature work, and refactoring, requiring clear testing guidelines and structured steps from test creation to implementation and refactor.

Does test-driven development require both integration and end-to-end tests?▼

Yes, test-driven development under this workflow requires unit, integration, and end-to-end tests to meet the minimum 80% coverage target and adequately cover edge cases.

What's the best way to structure a workflow from user story to test creation?▼

The best way to structure this workflow is to follow end-to-end guidance from user story to test creation, implementation, validation, and finally refactor, ensuring tests are written first.