tdd-workflow

Name: tdd-workflow
Availability: InStock
Author: Liam

Enforce a TDD workflow with unit, integration, and end-to-end tests at 80% coverage.

Updated Feb 13, 2026

Search Tags:#unit tests #testing #tdd #integration tests #code coverage #e2e tests #playwright

Ready to run

npx skills add https://github.com/LiamVDB1/opencode-config --skill tdd-workflow-liamvdb1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/LiamVDB1/opencode-config/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/LiamVDB1/opencode-config --skill tdd-workflow-liamvdb1

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures all code development adheres to Test-Driven Development (TDD) principles, guaranteeing high test coverage and robust software quality.

Core Features & Use Cases

TDD Enforcement: Guides developers to write tests before writing implementation code.
Comprehensive Testing: Mandates unit, integration, and E2E tests with a minimum of 80% coverage.
Use Case: When starting a new feature, use this skill to first define user journeys, write failing tests, implement code to pass, and verify coverage.

Quick Start

Use the tdd-workflow skill to ensure all new code follows test-driven development practices.

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 software features?▼

To enforce test-driven development, you must guide the process from user journey definition to writing failing tests, implementing code to pass, and verifying coverage. This approach ensures robust and reliable code by mandating tests before implementation.

What minimum code coverage is needed for unit and integration tests?▼

A minimum of 80% code coverage is needed for unit and integration tests. Comprehensive testing mandates creating unit, integration, and end-to-end tests to guarantee high test coverage and robust software quality throughout development.

How do I start writing tests before implementation code?▼

You start writing tests before implementation code by first defining user journeys, then generating test cases. This test-driven development workflow guides you to write failing tests initially, implement code to pass them, and finally verify coverage.

Does the TDD workflow include end-to-end tests using Playwright?▼

Yes, the TDD workflow includes end-to-end tests using Playwright. It mandates the creation of comprehensive tests, including unit, integration, and E2E tests, ensuring all code development adheres to Test-Driven Development principles.

What is the best way to structure a TDD workflow for robust code?▼

The best way to structure a TDD workflow for robust code is to mandate test creation across unit, integration, and end-to-end levels. Guide the process from user journey definition and test case generation to code implementation, refactoring, and coverage verification.