tdd-workflow

Enforce a RED-GREEN-REFACTOR cycle with gate hooks and evidence tracking for TDD tasks.

4|Updated Jan 8, 2026

Search Tags:#tdd #test-driven development #evidence-tracking #verifier-guided #scoped-tests #gate-hooks

Ready to run

npx skills add https://github.com/mnthe/hardworker-marketplace --skill tdd-workflow-mnthe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/mnthe/hardworker-marketplace/tree/main/plugins/ultrawork/skills/tdd-workflow
Command: npx skills add https://github.com/mnthe/hardworker-marketplace --skill tdd-workflow-mnthe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enforces a strict Test-Driven Development workflow for ultrawork tasks by ensuring tests are written before code, mandating a RED-GREEN-REFACTOR cycle, and capturing verifiable evidence to support task completion.

Core Features & Use Cases

Enforces RED-GREEN-REFACTOR lifecycle with gate hooks to prevent out-of-order work.
Supports task-scoped testing via dedicated test_scope guidance and scoped execution.
Integrates with the ultrawork evidence flow to document test creation, failures, minimal implementations, and refactors.
Provides concrete guidance for handling tests and implementation steps within TDD tasks, ensuring traceability and repeatability.

Quick Start

Mark a task as approach: "tdd" to activate the TDD workflow.
Create a failing test first (RED), then implement the minimal code to pass (GREEN), and optionally refactor (REFACTOR).
Record evidence at each step (test creation, test failure, implementation, pass status, and any refactoring) to maintain the TDD Evidence Chain.

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 cycle for test-driven development tasks?▼

Test-driven development rigor is enforced using gate hooks that prevent out-of-order work, ensuring you write failing tests first, implement minimal code to pass, and then refactor while preserving tests.

What is evidence tracking in a TDD workflow and why do I need it?▼

Evidence tracking in a TDD workflow captures verifiable proof of test creation, failures, minimal implementations, and refactors to document task completion and ensure full traceability across the development lifecycle.

How do I activate TDD task scoping and scoped test execution?▼

TDD task scoping activates by marking tasks with approach 'tdd' in ultrawork workflows, which triggers dedicated test_scope guidance and scoped execution commands to isolate and run specific tests.

Can I integrate test-driven development tasks with my existing ultrawork evidence flow?▼

Yes, test-driven development tasks integrate directly with the ultrawork evidence flow to document test creation, failures, pass statuses, and refactoring steps, maintaining a verifiable TDD Evidence Chain.

When should I use gate hooks for test-driven development instead of standard testing?▼

Gate hooks for test-driven development should be used when you need strict enforcement of the RED-GREEN-REFACTOR sequence to prevent skipping steps, whereas standard testing allows more flexible, less traceable workflows.