tdd-workflow

Enforce Red → Green → Refactor commit cycles with TDD compliance checks before merging.

Updated Dec 23, 2025

Search Tags:#testing #tdd #metrics #red-green-refactor #ci #commit-discipline

Ready to run

npx skills add https://github.com/vineethsoma/agent-packages --skill tdd-workflow-vineethsoma

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, jq, bc, and includes scripts (resource) components.

What problem does it solve?

This skill enforces a formal Test-Driven Development workflow, ensuring tests are written before code and that all changes are tracked via Red → Green → Refactor commit cycles, preventing regression and improving code quality.

Core Features & Use Cases

Test-first discipline: Guarantees tests are written prior to implementation.
Commit pattern enforcement: Tracks and promotes Red → Green → Refactor commits for visibility and metrics.
Compliance tooling: Provides scripts to initialize checklists, collect TDD metrics, and validate discipline.
Team collaboration: Guides multiple engineers through coordinated TDD cycles and shared templates.
CI readiness: Aligns unit tests and integration checks to enable safe merges.

Quick Start

Initialize TDD checklist for a story: ./scripts/init-tdd-checklist.sh us-001
Gather TDD metrics: ./scripts/gather-tdd-metrics.sh us-001
Validate compliance before merge: ./scripts/validate-tdd-compliance.sh us-001

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 Red-Green-Refactor TDD workflow for my team?▼

To enforce a strict TDD workflow, this skill mandates Red-Green-Refactor commit cycles using compliance scripts and checklists. It tracks test-first development through pre-merge validation to prevent regression and ensure code quality.

Can I validate TDD compliance before merging a feature branch?▼

Yes, you can validate TDD compliance before merging by running the provided validation scripts. The tool checks for proper commit patterns and test discipline, ensuring CI readiness and safe integration of new code.

How do I gather metrics for Test-Driven Development cycles?▼

You can gather TDD metrics by running the designated collection scripts against a specific story ID. This captures your team's test-first discipline data, providing visibility into Red-Green-Refactor execution and compliance.

Does this TDD enforcement workflow require specific command-line dependencies?▼

Yes, the TDD workflow requires git, jq, and bc dependencies installed in your environment. These command-line tools support the scripts that initialize checklists, gather metrics, and validate pre-merge compliance.

What is the best way to track test-first development discipline across multiple engineers?▼

The best way to track test-first development across multiple engineers is using coordinated TDD cycles with shared templates. This skill guides teams through formal commit patterns, ensuring consistent test-first design and auditability.

When should I not use a strict Red-Green-Refactor commit cycle?▼

You should avoid strict Red-Green-Refactor commit cycles when rapid prototyping without regression checks is needed, or if your environment lacks the required git, jq, and bc dependencies to run the compliance validation scripts.