tdd-workflow (测试驱动开发工作流)

Enforce a Test-Driven Development workflow requiring tests before implementation.

3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/ahiendz/DuAnCuoiKhoa --skill tdd-workflow-ahiendz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow (测试驱动开发工作流)
Source: https://github.com/ahiendz/DuAnCuoiKhoa/tree/main/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/ahiendz/DuAnCuoiKhoa --skill tdd-workflow-ahiendz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures code quality and maintainability by enforcing tests before code, reducing regressions and enabling safer, faster refactors across feature development, bug fixes, and restructuring.

Core Features & Use Cases

  • Establishes a repeatable TDD workflow: plan tests before implementation, write unit tests, implement code, run tests, and refactor.
  • Supports unit, integration, and end-to-end testing, with guidance and examples for API endpoints and UI flows.
  • Promotes test design discipline, isolation, and measurable coverage targets (e.g., 80%+).

Quick Start

Write a failing unit test for a new feature and then implement the code to pass it.

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 for feature development?

A test-driven development workflow requires tests to exist before implementation, demanding at least 80% test coverage and a repeatable cycle from planning through testing, implementation, and refactoring.

What's the best way to maintain code quality and reduce regressions during refactoring?

The best way to reduce regressions is enforcing tests before code implementation, which enables safer and faster refactors across feature development, bug fixes, and restructuring.

Can I apply test-driven development to API endpoints and UI flows?

Yes, test-driven development applies to API endpoints and UI flows by supporting unit, integration, and end-to-end testing across these specific use cases with dedicated guidance and examples.

Does this test-driven development workflow support integration and e2e testing?

Yes, the test-driven development workflow supports unit, integration, and end-to-end testing, providing specific guidance and examples for API endpoints and UI flows.

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

To start test-driven development for a new feature, write a failing unit test first, then implement the code required to pass that test, and finally refactor while maintaining 80%+ coverage.

What test coverage percentage should I aim for in test-driven development?

Test-driven development demands at least 80% test coverage to ensure code quality, maintainability, and measurable test design discipline across the entire workflow.