tdd-workflow

Enforce test-driven development with unit, integration, and Playwright E2E tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces test-driven development by ensuring tests drive code changes.

Core Features & Use Cases

  • TDD First: Always write tests before implementing code.
  • Coverage Goal: Achieve 80%+ coverage across unit, integration, and E2E tests.
  • Test Types: Unit, integration, and E2E (Playwright) tests.

Quick Start

Begin a new feature by writing tests first and then implementing code until the 80%+ coverage goal is met.

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 for new features and bug fixes?

To enforce test-driven development, you must write unit, integration, and E2E tests before implementing code changes. This approach ensures tests drive feature development, bug fixes, refactoring, and API changes until achieving 80%+ coverage.

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

The best way to achieve 80%+ coverage is by writing tests first during development and refactoring. You must implement unit, integration, and Playwright E2E tests continuously until the 80%+ coverage goal is met for the target code.

Does this TDD workflow use Playwright for browser-based end-to-end tests?

Yes, this TDD workflow uses Playwright specifically for browser-based end-to-end tests. It requires writing Playwright E2E tests alongside unit and integration tests to ensure comprehensive coverage and validate application behavior.

Can I apply test-driven development when refactoring existing code or changing APIs?

Yes, you can apply test-driven development when refactoring existing code or changing APIs. The workflow ensures tests drive code changes across feature development, bug fixes, refactoring, and API modifications to maintain 80%+ coverage.