tdd-workflow

Enforce test-driven development with RED-to-GREEN validation and Git checkpoint commits.

7|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/chenziyang110/spec-kit-plus --skill tdd-workflow-chenziyang110
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/chenziyang110/spec-kit-plus/tree/main/templates/passive-skills/tdd-workflow
Command: npx skills add https://github.com/chenziyang110/spec-kit-plus --skill tdd-workflow-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The tdd-workflow skill solves unreliable code changes by enforcing a strict test-first, evidence-backed development loop with strong coverage expectations.

Core Features & Use Cases

  • Test-first implementation: Require a RED gate before any production code changes, then re-run the same relevant tests to reach GREEN.
  • Coverage and test-type discipline: Enforce a minimum 80%+ coverage goal across unit, integration, and E2E (including Playwright) tests, with edge cases and error paths covered.
  • Evidence-focused Git checkpoints: Create checkpoint commits after RED, GREEN, and optional refactors (on the current active branch) with commit messages that capture the exact stage outcomes.

Use cases include developing new features, fixing bugs, refactoring safely, adding API endpoints, and building new components with confidence that regressions are caught.

Quick Start

Activate tdd-workflow by telling your AI coding agent: "Use TDD to implement this change, ensure the targeted tests fail first (RED), implement the minimal fix, rerun tests to get GREEN, and then verify 80%+ 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 test-driven development with strict test coverage in my workflow?

Enforcing test-driven development requires a strict RED-to-GREEN validation loop before shipping changes, maintaining at least 80% combined test coverage across unit, integration, and E2E tests.

How do I create Git checkpoint commits that validate test-first implementation stages?

Creating evidence-based Git checkpoint commits involves committing after RED, GREEN, and optional refactor stages on the active branch, using commit messages that capture exact stage outcomes.

Does test-driven development workflow support Playwright browser flows and API integration testing?

Test-driven development workflow supports API integration testing and Playwright browser flows, applying test-first validation to unit, integration, and end-to-end testing scenarios.

How do I use Jest and Vitest to ensure edge cases and error paths are covered during refactoring?

Using Jest and Vitest ensures edge cases, error paths, and boundary conditions are covered by enforcing a minimum 80% coverage goal and requiring failing tests before implementing minimal fixes.

What is the best way to prevent unsafe code changes when fixing bugs or adding new features?

Preventing unsafe code changes when fixing bugs or adding features requires test-first implementation, evidence-backed Git checkpoints, and a minimum 80% combined coverage to catch regressions.

Can I use TDD workflow to maintain test coverage discipline across unit and E2E tests?

TDD workflow maintains test coverage discipline by enforcing an 80%+ coverage goal across unit, integration, and E2E tests, ensuring edge cases and error paths are validated before shipping.