tdd-workflow

Enforce Test-Driven Development with 80% code coverage across unit, integration, and end-to-end tests.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/ndhananj/codex-agent-setup --skill tdd-workflow-ndhananj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/ndhananj/codex-agent-setup/tree/main/docs/zh-CN/skills/tdd-workflow
Command: npx skills add https://github.com/ndhananj/codex-agent-setup --skill tdd-workflow-ndhananj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces Test-Driven Development (TDD) to ensure code quality, reduce bugs, and enable confident refactoring by mandating comprehensive test coverage.

Core Features & Use Cases

  • Test-First Development: Guides the process of writing tests before implementation.
  • Comprehensive Testing: Encompasses unit, integration, and end-to-end tests.
  • Coverage Mandate: Requires a minimum of 80% code coverage.
  • Use Case: When developing a new feature, use this Skill to ensure that robust tests are written first, leading to a more stable and maintainable codebase.

Quick Start

Follow the TDD workflow to develop new features and ensure high test coverage.

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 writing new features?

Test-Driven Development workflow guides you through writing tests before implementation, adding minimal code to pass tests, and refactoring for quality. It enforces a minimum 80% code coverage across unit, integration, and end-to-end testing phases during feature development.

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

Yes, this TDD workflow supports integration and end-to-end testing with Playwright. It guides you through comprehensive testing patterns, ensuring your test-first development achieves the mandated 80% code coverage across unit, integration, and end-to-end tests.

Can I use Vitest and Jest for unit testing with this Test-Driven Development process?

Yes, you can use Vitest and Jest for unit testing within this Test-Driven Development process. The workflow explicitly supports both Jest and Vitest patterns to help you write tests before code and achieve the required 80% coverage.

What is the best way to maintain 80% code coverage during refactoring?

The best way to maintain 80% code coverage during refactoring is following the TDD cycle: write tests first, implement minimal code to pass, and refactor confidently. This ensures your refactoring does not break existing unit, integration, or end-to-end tests.

When do I need to write tests before code for bug fixes?

You need to write tests before code for bug fixes when enforcing Test-Driven Development. By writing a failing test that reproduces the bug first, you can implement the fix and ensure the updated code passes the test while maintaining 80% coverage.