tdd-workflow

Enforce test-driven development workflows with tests before implementation and 80% coverage.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/giuseppecutuli/speakdoc --skill tdd-workflow-giuseppecutuli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/giuseppecutuli/speakdoc/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/giuseppecutuli/speakdoc --skill tdd-workflow-giuseppecutuli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures development follows Test-Driven Development (TDD) with comprehensive test coverage, reducing bugs and enabling confident refactoring.

Core Features & Use Cases

  • Enforces Test-Driven Development: write tests before code.
  • Provides a structured workflow for unit, integration, and E2E tests.
  • Guides achieving minimum 80% coverage with edge cases and error paths.
  • Step-by-step TDD workflow from user journeys to refactor.

Quick Start

Start by writing user journeys and test cases, then implement code to satisfy tests and achieve 80%+ 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 workflows for feature development?▼

Test-driven development workflows are enforced by requiring tests to be written before implementation. This applies to feature development, bug fixes, refactoring, and API or component creation, guiding you through a structured step-by-step process.

What is the best way to achieve 80% test coverage with unit, integration, and e2e testing?▼

Achieving 80% test coverage requires utilizing structured test patterns that include edge cases and error paths. You can reach this by following a step-by-step workflow that covers unit, integration, and Playwright-based E2E tests.

Can I use Playwright for E2E testing when following a TDD workflow?▼

Yes, Playwright is supported for E2E testing within the TDD workflow. The workflow provides specific examples for Playwright-based E2E tests alongside unit and integration tests to ensure comprehensive coverage.

How do I start writing tests before implementation for bug fixes and refactoring?▼

Start by writing user journeys and test cases first, then implement the code to satisfy those tests. This ensures bug fixes and refactoring follow test-driven development principles before any functional code changes are made.

Does this TDD workflow apply to API and component creation?▼

Yes, this TDD workflow directly applies to API and component creation. It enforces writing tests before code implementation across these development tasks to reduce bugs and enable confident refactoring.