tdd-flow

Orchestrate TDD-based feature changes from plan files or text requests.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/yAtomtom/dotfiles --skill tdd-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-flow
Source: https://github.com/yAtomtom/dotfiles/tree/main/.claude/skills/tdd-flow
Command: npx skills add https://github.com/yAtomtom/dotfiles --skill tdd-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables implementing or modifying features in existing projects using a disciplined TDD workflow, ensuring changes are validated by tests before integration.

Core Features & Use Cases

  • Plan-driven execution: Drives feature work from a plan file or a text change request, preserving step order.
  • Deterministic testing orchestration: Coordinates test creation, execution, and verification across multiple stages.
  • Safety and reporting: Stops on failures with actionable reports and prevents unsafe automation.

Quick Start

Provide a plan file path (or a change request) and let the TDD flow orchestrate the tasks.

Frequently Asked Questions about tdd-flow

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

FAQPage Schema
How do I automate test-driven development for feature changes in an existing project?

You can automate test-driven development by orchestrating plan-driven workflows that coordinate test creation, execution, and verification step-by-step. This approach applies deterministic testing to validate feature modifications before integrating them into your existing project.

What is the best way to execute a TDD workflow from a plan file?

The best way to execute a TDD workflow from a plan file is using plan-driven orchestration that parses requirements and preserves step order. This ensures tasks like adding functionality or modifying code paths follow a deterministic, test-validated sequence.

Can I use text-based change requests to drive test-driven feature modifications?

Yes, you can use text-based change requests to drive test-driven feature modifications alongside plan files. The orchestration process parses these requests to manage stepwise execution and validate code changes through structured testing stages.

How does testing orchestration handle failures during automated feature development?

Testing orchestration handles failures by implementing safety guards that immediately halt execution upon test failures. It generates actionable reports detailing the failure, preventing unsafe automation from proceeding with unvalidated code changes.

Do I need a predefined plan to automate test-driven development workflows?

You do not strictly need a predefined plan to automate test-driven development workflows. You can alternatively provide a text change request, which the orchestration engine parses to drive stepwise execution and task-id handling for your feature updates.