tdd-workflow

Enforces red-green-refactor TDD cycles with automated test execution and coverage validation across multiple languages.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/mathiasbourgoin/roster --skill tdd-workflow-mathiasbourgoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/mathiasbourgoin/roster/tree/main/.opencode/skills/tdd-workflow
Command: npx skills add https://github.com/mathiasbourgoin/roster --skill tdd-workflow-mathiasbourgoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of untested, brittle code by enforcing a strict test-driven development (TDD) cycle, ensuring every new feature or bug fix is validated by failing tests before any implementation work begins.

Core Features & Use Cases

  • Strict Red-Green-Refactor Enforcement: Prevents writing implementation code before a failing test exists, and stops users from modifying tests to make failing code pass.
  • Multi-Framework Auto-Detection: Automatically identifies the project's test runner (Vitest, Jest, pytest, cargo test, go test, and more) to run the correct test commands.
  • Coverage Validation: Checks test coverage after implementation and flags untested code paths if coverage falls below the default 80% threshold.
  • Use Case: When adding a new user profile editing feature, use this Skill to write a failing test for profile updates first, implement the minimal required logic, refactor for clarity, and verify all existing tests still pass.

Quick Start

Use the tdd-workflow skill to implement the new password reset feature outlined in the project requirements.

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 cycle for new features and bug fixes?

You can enforce test-driven development by applying a strict red-green-refactor cycle that requires a failing test to exist before any implementation code is written, preventing untested or brittle logic from entering your project.

Does this TDD workflow support multiple languages and test frameworks like pytest and cargo test?

Yes, test-driven development supports cross-language workflows by automatically detecting and running common test frameworks including JavaScript tools like Vitest and Jest, alongside Python's pytest, Rust's cargo test, Go test, and OCaml.

How do I validate test coverage and ensure untested code paths are flagged during TDD?

Test coverage is validated by executing the full test suite after each code change and automatically flagging untested code paths if your coverage falls below the default 80% threshold.

What is the red-green-refactor cycle and how does it prevent modifying tests to make failing code pass?

The red-green-refactor cycle is a strict test-driven development process that requires writing a failing test first, implementing minimal logic to pass it, and refactoring, while actively stopping users from modifying tests to force passing code.

Can I use this test-driven development approach for both new software features and bug fixes?

Yes, strict test-driven development applies to both new software features and bug fixes, ensuring every code change is validated by a failing test before implementation work begins to eliminate untested code.