tdd-workflow

Enforce test-driven development with gate-based workflows and 80% test coverage.

3|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/nassimbf/ftitos-claude-code --skill tdd-workflow-nassimbf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/nassimbf/ftitos-claude-code/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/nassimbf/ftitos-claude-code --skill tdd-workflow-nassimbf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures all code development follows TDD principles with comprehensive test coverage.

Core Features & Use Cases

  • Enforces tests-first development across unit, integration, and E2E to maintain high quality.
  • Provides a structured workflow with explicit gates and checkpoint commits to guide teams.
  • Helps teams maintain discipline during feature development, bug fixes, and refactors.

Quick Start

Run the TDD workflow to enforce tests first and validate coverage before code changes.

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

To enforce test-driven development, you need a structured workflow with explicit gates, checkpoint commits, and deterministic validation of RED-GREEN progress. This ensures tests are written first and validated before code changes proceed.

How do I maintain TDD discipline during feature development and refactoring?

Maintaining TDD discipline during feature development and refactoring requires applying a gate-based workflow that validates RED-GREEN progress at deterministic checkpoints, ensuring comprehensive test coverage before integration.

What is the best way to ensure 80%+ test coverage across unit, integration, and E2E tests?

The best way to ensure 80%+ test coverage is to enforce broad unit, integration, and end-to-end testing through a tests-first workflow that validates coverage at deterministic checkpoints before code changes are accepted.

Does this TDD workflow support bug fixes and refactoring?

Yes, this TDD workflow explicitly supports bug fixes and refactoring by applying test-driven development principles to ensure high code quality and broad test coverage during these specific tasks.

How do I validate RED-GREEN progress in a test-driven development workflow?

Validating RED-GREEN progress requires a gate-based workflow with deterministic checkpoints and checkpoint commits, ensuring the test fails before implementation and passes after, enforcing strict tests-first development.