tdd-workflow

Enforce Test-Driven Development with tests before implementation and 80% coverage.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/unju-ai/ecc --skill tdd-workflow-unju-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/unju-ai/ecc/tree/main/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/unju-ai/ecc --skill tdd-workflow-unju-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enforces a rigorous Test-Driven Development (TDD) process to ensure code quality, maintainability, and high test coverage across unit, integration, and end-to-end tests.

Core Features & Use Cases

  • Enforces TDD: Guides users to write tests before writing implementation code.
  • Comprehensive Coverage: Mandates a minimum of 80% code coverage, including unit, integration, and E2E tests.
  • Structured Workflow: Provides clear steps for defining user journeys, generating tests, implementing code, and verifying coverage.
  • Use Case: When developing a new API endpoint, use this skill to first define the expected request/response and error scenarios with tests, then write the minimal code to pass those tests, and finally refactor and verify coverage.

Quick Start

Activate this skill when starting any new feature development or bug fix to ensure tests are written before code.

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 when building a new API endpoint?

To enforce test-driven development, you define expected request, response, and error scenarios with tests first, write minimal code to pass those tests, then refactor and verify coverage. This ensures reliable code delivery before implementation begins.

What is the minimum code coverage required for unit, integration, and e2e tests?

The minimum code coverage required is 80% across unit, integration, and end-to-end tests. This comprehensive coverage mandate ensures high code quality and maintainability throughout the development process.

How do I structure test case generation and mock external services?

Structure test case generation by defining user journeys first, then generating tests for those paths. Mock external services during this generation phase to isolate components and ensure tests validate code logic without external dependencies.

When should I start writing tests before implementation code?

You should start writing tests before implementation when beginning any new feature development or bug fix. Activating this workflow at the start ensures tests dictate the code structure, yielding maintainable and reliable results.

Does test-driven development work with continuous integration for reliable code delivery?

Test-driven development works seamlessly with continuous integration to ensure reliable code delivery. By mandating tests before implementation and verifying coverage, the workflow validates code quality automatically during the integration process.