tdd-workflow

Enforce test-driven development with tests before code and Git checkpoints.

Updated Mar 16, 2026

Search Tags:#testing #tdd #playwright #quality-assurance #unit-tests #integration-tests #e2e-tests

Ready to run

npx skills add https://github.com/Clean1ines/crm_bot --skill tdd-workflow-clean1ines

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Clean1ines/crm_bot/tree/main/.agents/skills/ecc/tdd-workflow
Command: npx skills add https://github.com/Clean1ines/crm_bot --skill tdd-workflow-clean1ines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Test-Driven Development Workflow ensures code changes are guided by tests, preventing regressions and improving reliability across features, bug fixes, and refactors.

Core Features & Use Cases

Enforces tests before code across unit, integration, and end-to-end scopes.
Provides a structured Git checkpoint process to document progress and evidence.
Useful for teams adopting TDD in feature development, debugging, and API/component creation with strong quality gates.

Quick Start

Describe a feature to trigger the TDD workflow and generate the corresponding tests.

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 across my software projects?▼

Test-driven development is enforced by requiring tests before writing code and maintaining high coverage. This ensures code changes are guided by tests, preventing regressions across features, bug fixes, and refactoring work.

Does this TDD workflow support end-to-end testing with Playwright?▼

End-to-end testing with Playwright is fully supported. The workflow accommodates unit, integration, and end-to-end testing scopes to maintain strong quality gates across API endpoints, components, and services.

Can I use this workflow for refactoring existing code and fixing bugs?▼

Yes, the workflow applies to refactoring existing code and fixing bugs. It guides code changes by requiring tests beforehand, ensuring reliability and preventing regressions during feature development and debugging.

How do I document test progress and evidence when following a TDD workflow?▼

Test progress and evidence are documented in commits using a structured Git checkpoint process. Git checkpoints are required after each stage of the test-driven development workflow to record progress.

What are the limitations of enforcing high test coverage for API endpoints and components?▼

High test coverage enforcement applies strictly to API endpoints, components, and services within typical software teams. The workflow requires Git checkpoints after each stage, which may alter existing deployment speeds.