tdd-workflow

Enforces a test-first workflow with the RED-GREEN-REFACTOR cycle.

Updated Feb 17, 2026

Search Tags:#code quality #testing #tdd #development workflow #refactoring #agile

Ready to run

npx skills add https://github.com/mscipio/bilt-transactions-export --skill tdd-workflow-mscipio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/mscipio/bilt-transactions-export/tree/main/.opencode/skills/tdd-workflow
Command: npx skills add https://github.com/mscipio/bilt-transactions-export --skill tdd-workflow-mscipio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a strict Test-Driven Development (TDD) workflow, ensuring that all new code is written only after a failing test has been created and observed, preventing regressions and improving code quality.

Core Features & Use Cases

Test-First Enforcement: Mandates writing tests before any implementation code.
TDD Cycle Guidance: Provides clear steps for the RED-GREEN-REFACTOR cycle.
Use Case: When implementing a new user authentication feature, you would first write a test for the login success scenario. This test would fail initially. Then, you write the minimal code to make the test pass, followed by refactoring.

Quick Start

Use the tdd-workflow skill to implement the new user registration feature by writing a failing test first.

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 feature implementation?▼

TDD cycle guidance provides clear steps for the RED-GREEN-REFACTOR cycle, ensuring you write tests before implementation code and refactor only after achieving a passing test state.

What is the best way to prevent regressions when fixing bugs in an agile development workflow?▼

The best way to prevent regressions during bug fixes is adopting a strict test-first approach, requiring a failing test to be created and observed before writing any production code to fix the issue.

Can I use this workflow for both new features and bug fixes?▼

Yes, this workflow enforces a strict test-driven development process for all new feature implementation and bug fixes alike, ensuring consistent code quality and preventing regressions across tasks.

How do I start implementing a new feature using a test-first approach?▼

To start implementing a feature using a test-first approach, write a failing test for the desired scenario first. Then, write the minimal code required to make the test pass, followed by refactoring.

Why does test-first development require observing a failing test before writing code?▼

Observing a failing test before writing code ensures the test accurately verifies the new behavior, preventing regressions and guaranteeing that implementation code is written only after a valid test exists.