tdd-workflow

Enforces a Test-Driven Development workflow with test-first and coverage requirements.

Updated Feb 17, 2026

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

Ready to run

npx skills add https://github.com/Gatsbyhateyou/gatsby-website --skill tdd-workflow-gatsbyhateyou

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Gatsbyhateyou/gatsby-website/tree/main/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/Gatsbyhateyou/gatsby-website --skill tdd-workflow-gatsbyhateyou

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enforces a rigorous Test-Driven Development (TDD) process to ensure code quality, maintainability, and high test coverage across unit, integration, and end-to-end tests.

Core Features & Use Cases

Mandatory Test-First Development: Guides users to write tests before writing implementation code.
Comprehensive Test Coverage: Enforces a minimum of 80% coverage across all test types.
Structured TDD Workflow: Provides clear steps for user journey definition, test case generation, implementation, and refactoring.
Use Case: When developing a new API endpoint, use this skill to first define the expected request/response and error scenarios in tests, then write the minimal code to pass those tests, ensuring the endpoint is robust and well-tested from the start.

Quick Start

Follow the TDD workflow steps outlined in this skill to write tests before implementing new code.

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-first workflow when building new API endpoints?▼

To enforce a test-first workflow, define the expected request, response, and error scenarios in tests before writing any implementation code. This approach ensures your API endpoints are robust and well-tested from the very start by mandating test creation prior to development.

What is the recommended code coverage percentage for unit and integration tests?▼

The recommended code coverage is a minimum of 80% across all test types, including unit, integration, and end-to-end tests. Enforcing this specific coverage threshold ensures high code quality and maintainability throughout the software development process.

How do I structure end-to-end tests using Playwright within a TDD workflow?▼

To structure end-to-end tests using Playwright within a TDD workflow, first define user journeys and generate test cases. You then write the minimal implementation code required to pass those specific end-to-end tests, followed by refactoring and verifying coverage metrics.

Can I use Jest for unit and integration tests while following this TDD process?▼

Yes, you can use Jest for unit and integration tests. The TDD workflow specifies testing patterns for Jest to guide you through defining test cases, implementing code to pass tests, refactoring, and verifying that coverage metrics meet the required standards.

What are the steps to write tests before implementation code effectively?▼

The steps to write tests before implementation code effectively involve defining user journeys, generating test cases, writing minimal code to pass those tests, refactoring the code, and finally verifying coverage metrics to ensure comprehensive testing across all layers.