tdd-workflow

Enforce test-driven development workflows with RED/GREEN checkpoints and commit-based evidence.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/khunglong-03/Pathora_Version3 --skill tdd-workflow-khunglong-03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/khunglong-03/Pathora_Version3/tree/main/.cursor/skills/tdd-workflow
Command: npx skills add https://github.com/khunglong-03/Pathora_Version3 --skill tdd-workflow-khunglong-03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide codifies a repeatable test-driven development workflow to prevent late defect discovery by ensuring tests drive design and implementation.

Core Features & Use Cases

  • Enforces writing unit, integration, and end-to-end tests before code is implemented.
  • Provides structured steps for RED/GREEN cycles, checkpoint commits, and test coverage targets.
  • Applies to feature development, bug fixes, refactoring, and API changes to uphold quality standards.

Quick Start

Outline tests first for a new feature, then implement code to satisfy them.

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 to reduce code defects?

Enforcing a test-driven development workflow involves defining RED/GREEN checkpoints and commit-based evidence to ensure tests drive design and implementation, reducing late defect discovery. You outline unit, integration, and E2E tests before writing feature code.

What is the RED/GREEN cycle in TDD and how does it guide implementation?

The RED/GREEN cycle in TDD is a testing pattern where you first write failing tests (RED), then implement code to satisfy them (GREEN). This step-by-step pattern ensures your software engineering workflow produces code guided by test requirements.

How do I apply TDD to bug fixes and refactoring without breaking existing features?

TDD applies to bug fixes and refactoring by outlining tests first to verify the issue or structural change, then implementing code to satisfy them. This maintains quality standards and prevents regressions across unit, integration, and end-to-end tests.

Can I use this TDD workflow for both feature development and API changes?

Yes, this TDD workflow applies to feature development, bug fixes, refactoring, and API changes. It upholds quality standards by enforcing structured testing steps and coverage targets across unit, integration, and E2E tests before implementation.

What's the best way to start test-driven development for a new feature?

The best way to start test-driven development for a new feature is to outline tests first, establishing coverage targets and checkpoint commits. You then implement code step-by-step to satisfy the RED/GREEN testing cycles.

When should I use checkpoint commits during my testing workflow?

Checkpoint commits should be used during your testing workflow to provide commit-based evidence for RED/GREEN cycles. They document step-by-step testing patterns and ensure test coverage targets are met before moving forward with implementation.