tdd-workflow

Enforce a test-driven development workflow with RED and GREEN validation.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/PequiProject/pequi --skill tdd-workflow-pequiproject
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/PequiProject/pequi/tree/main/.agents/skills/testing
Command: npx skills add https://github.com/PequiProject/pequi --skill tdd-workflow-pequiproject

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a structured test-driven development workflow, ensuring tests precede production code and guiding teams toward reliable, maintainable software.

Core Features & Use Cases

  • Enforces writing tests before code to drive design and prevent regressions.
  • Maintains 80%+ test coverage across unit, integration, and end-to-end tests.
  • Provides a repeatable workflow from defining journeys to validating RED and GREEN, including refactoring and coverage checks.

Quick Start

Begin by writing a failing test for the feature, then implement the minimal code required to pass it.

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 strict test-driven development workflow in my project?

To enforce a strict test-driven development workflow, you must write failing tests before implementing production code, validate the RED stage, write minimal code to pass, and validate the GREEN stage with clear evidence collection.

What is the best way to maintain 80%+ test coverage across unit and end-to-end tests?

Maintaining 80%+ test coverage requires measuring validation across unit, integration, and end-to-end tests after defining journeys and refactoring, ensuring all code paths are verified through Git-based checkpoint commits.

How do I guide my team through RED and GREEN validation stages in CI/CD pipelines?

Guiding teams through RED and GREEN validation in CI/CD pipelines requires clear evidence collection to verify the failing test state and passing implementation state at each Git-based checkpoint commit.

Does this TDD workflow require Git-based checkpoint commits for refactoring?

Yes, this TDD workflow requires Git-based checkpoint commits during refactoring to structurally separate the minimal code implementation phase from subsequent test coverage measurement and optimization.

Can I use Playwright for end-to-end testing within a structured TDD workflow?

Yes, you can use Playwright for end-to-end testing within this workflow, which guides teams from defining user journeys to validating test coverage across unit, integration, and end-to-end environments.

Why write tests before code when implementing new features?

Writing tests before code drives software design and prevents regressions by forcing a strict test-driven development cycle, ensuring the minimal code required to pass is implemented only after the RED stage is validated.