practice-tdd

Manage Red, Green, and Refactor TDD phases with lock files and changelog markers.

Updated Apr 13, 2026

Search Tags:#workflow #tdd #changelog #software-engineering #phase-management #lock-files #test-integrity

Ready to run

npx skills add https://github.com/GarethJB/workflow-plugin --skill practice-tdd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: practice-tdd
Source: https://github.com/GarethJB/workflow-plugin/tree/main/skills/practice-tdd
Command: npx skills add https://github.com/GarethJB/workflow-plugin --skill practice-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tightly orchestrates a disciplined Test-Driven Development (TDD) workflow by enforcing phase boundaries and changelog discipline to prevent test-implementation contamination.

Core Features & Use Cases

Phase-separated Red/Green/Refactor workflow with lock files to guard transitions
Changelog markers per phase to allow session resumption after interruption
Optional guard rails to prevent edits outside permitted phases and protect test integrity

Quick Start

Start a TDD session by entering the Red phase and let the system manage phase locks, transitions, and changelog updates through Green and Refactor.

Frequently Asked Questions about practice-tdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce strict separation between Red, Green, and Refactor phases in a TDD workflow?▼

TDD phase separation is enforced by applying lock files that prevent code edits outside the currently active phase. This protects test integrity by ensuring Red, Green, and Refactor stages remain strictly isolated throughout your workflow.

What is the best way to resume a Test-Driven Development session after an interruption?▼

Resuming an interrupted TDD session is handled through changelog markers recorded during each phase. These markers trace progress and allow the workflow to pick up exactly where the previous session left off without losing context.

How do TDD phase locks prevent cross-contamination between tests and implementation?▼

TDD phase locks prevent cross-contamination by creating active phase files that restrict edits to the current stage. This ensures test code is not modified during implementation and vice versa.

Can I maintain TDD phase discipline across multiple development sessions?▼

TDD phase discipline can be maintained across multiple sessions through locked-phase enforcement and traceable changelogs. The system manages transitions and updates logs so context is preserved between distinct working periods.

What are the limitations of using lock files for TDD phase management?▼

Lock file limitations include dependency on strict adherence to phase transition rules and potential blocking if lock files are not properly released. Optional guard rails are needed to prevent edits outside allowed phases.