tdd-workflow

Enforce Test-Driven Development workflows with Git checkpoints and 80% test coverage.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/Long-NguyenHai/warehouse-ai --skill tdd-workflow-long-nguyenhai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Long-NguyenHai/warehouse-ai/tree/main/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/Long-NguyenHai/warehouse-ai --skill tdd-workflow-long-nguyenhai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill ensures all code development follows Test-Driven Development (TDD) principles with extensive test coverage, reducing bugs and improving code quality.

Core Features & Use Cases

  • TDD Workflow Execution: Automates the TDD process, including planning, writing tests, implementing code, and refactoring.
  • Coverage Enforce: Mandates 80%+ coverage for unit, integration, and E2E tests.
  • Integration with Git: Uses Git checkpoints to verify code changes and progress through the TDD cycle.
  • Use Case: Ideal for developers looking to implement a TDD workflow in their projects, ensuring best practices are followed and code quality is maintained.

Quick Start

Activate the tdd-workflow skill with the path to your implementation plan: tdd-workflow <path/to/plan.md>.

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 workflows in my project?

Test-driven development workflows can be enforced by automating the TDD process from planning and writing tests to implementation and refactoring. This skill mandates strict TDD practices and uses Git checkpoints to verify code changes and progress through the TDD cycle.

How do I ensure my code has 80% or higher test coverage?

To ensure 80% or higher test coverage, you can apply automated coverage enforcement across unit, integration, and E2E tests. This skill mandates a strict 80%+ coverage threshold, reducing bugs by verifying that all code development follows rigorous testing principles.

Does this test-driven development workflow integrate with Git?

Yes, this test-driven development workflow integrates with Git by using checkpoints. These Git checkpoints verify code changes and track your progress as you move through the TDD cycle of writing tests, implementing code, and refactoring.

What do I need to start automating my TDD process?

To start automating your TDD process, you need an implementation plan file. You activate the workflow by providing the path to your plan file, which the system then uses to execute the test-driven development cycle and enforce coverage rules.

When should I use an automated TDD workflow instead of manual testing?

An automated TDD workflow should be used for software development processes requiring rigorous testing and high code quality. It is ideal when you need to enforce 80%+ coverage across unit, integration, and E2E tests while maintaining strict development practices.