tdd-workflow

Enforces a Test-Driven Development workflow with 80%+ test coverage.

14|Updated Sep 22, 2025
One-click install
npx skills add https://github.com/gtheys/opencode --skill tdd-workflow-gtheys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/gtheys/opencode/tree/main/coding/skills/tdd-workflow
Command: npx skills add https://github.com/gtheys/opencode --skill tdd-workflow-gtheys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing feature code without tests leads to fragile software and hard-to-change codebases. This skill enforces a Test-Driven Development approach to ensure tests guide implementation and maintain code quality.

Core Features & Use Cases

  • Enforces writing unit, integration, and E2E tests before code.
  • Maintains minimum 80% overall test coverage across all test types.
  • Provides a step-by-step TDD workflow with example test templates and practical guidance for real-world projects.

Quick Start

Describe your feature in plain language and start the TDD workflow by following the steps outlined in this skill.

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 test-driven development workflow for new features?

To enforce test-driven development, you must write unit, integration, and E2E tests before writing implementation code, run them to fail, and then refactor to maintain at least 80% overall test coverage.

What is the best way to ensure 80% test coverage when fixing bugs?

Ensuring 80% test coverage when fixing bugs requires writing tests first to reproduce the issue, implementing the fix to pass the tests, and verifying the overall coverage threshold across all test types.

Can I use Playwright for end-to-end testing in a strict TDD workflow?

You can use Playwright for end-to-end testing within a strict TDD workflow by writing E2E tests first to define expected behavior, then implementing the feature code until the Playwright tests pass.

How do I write unit tests before implementation code without breaking the build?

Writing unit tests before implementation code involves defining the expected API, running the tests to confirm they fail correctly, and then writing the minimum implementation logic required to make the unit tests pass.

Does strict test-driven development slow down refactoring tasks?

Strict test-driven development accelerates refactoring by providing a safety net of unit, integration, and E2E tests, allowing you to modify code confidently while ensuring existing functionality remains unbroken.