tdd-workflow

Enforce TDD workflows with Jest, Vitest, and Playwright for 80%+ coverage.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/shygoly/sapbase --skill tdd-workflow-shygoly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/shygoly/sapbase/tree/main/docs/zh-CN/skills/tdd-workflow
Command: npx skills add https://github.com/shygoly/sapbase --skill tdd-workflow-shygoly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces Test-Driven Development (TDD) across software projects, ensuring tests are written before code and that overall test coverage remains high across unit, integration, and end-to-end tests.

Core Features & Use Cases

  • Enforces a TDD workflow from requirement discovery to delivery, including writing user journeys, generating test cases, implementing code, and refactoring with confidence.
  • Targets 80%+ test coverage across unit, integration, and end-to-end tests, and validates edge cases and failure modes.
  • Supports full testing stack: Unit tests with Jest/Vitest, API/integration tests, and E2E tests with Playwright for browser automation.
  • Provides a repeatable, auditable process that reduces defects and accelerates safe refactoring.

Quick Start

Begin a new feature by writing a user journey and failing tests, then implement code to pass all tests.

Frequently Asked Questions about tdd-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a TDD workflow across unit, integration, and E2E tests?

To enforce a TDD workflow, you write user journeys and failing tests before implementation, targeting 80%+ coverage. This guided process applies to unit, integration, and end-to-end testing, ensuring code passes tests before refactoring.

Does this TDD workflow support Jest, Vitest, and Playwright?

Yes, the TDD workflow supports Jest and Vitest for unit testing, alongside Playwright for browser automation in end-to-end testing. It applies strict test coverage validation across these frameworks for API and integration scenarios.

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

The best way to maintain 80%+ test coverage during refactoring is using an auditable TDD process. By running pre-written unit, integration, and E2E tests, you validate edge cases and failure modes to accelerate safe code changes.

How do I start a new feature using test-driven development?

To start a new feature using test-driven development, begin by writing a user journey and generating failing test cases. You then implement the software code to pass all unit, integration, and E2E tests before delivery.

Why should I write failing tests before implementing code?

You should write failing tests before implementing code to establish a repeatable, auditable TDD workflow. This reduces defects by validating edge cases and failure modes early, ensuring high test coverage and confident refactoring.