tdd

Execute a strict TDD loop for tasks in tasks/todo.md.

1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Joaovsales/coding-agent-workflow --skill tdd-joaovsales
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/Joaovsales/coding-agent-workflow/tree/main/.agents/skills/tdd
Command: npx skills add https://github.com/Joaovsales/coding-agent-workflow --skill tdd-joaovsales

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a test-first discipline by driving a structured TDD loop for each task listed in tasks/todo.md, ensuring changes are guided by failing tests before implementation and tracked through checkpoints.

Core Features & Use Cases

  • Executes a repeated TDD loop for tasks found in tasks/todo.md, automatically generating a failing test, running tests, implementing minimal code, and validating a pass, followed by refactor and checkpointing.
  • Provides user checkpoints between steps to confirm progress and maintain accountability.
  • Integrates with specs in specs/ if available to inform required behavior.
  • Use case example: for a given task in tasks/todo.md, it will guide you through failing test creation, code changes, test verification, and completion status.

Quick Start

Start the TDD loop for the next task by invoking the TDD workflow and confirming each checkpoint as you progress.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I enforce a strict test-driven development loop for my project tasks?

You enforce a test-driven development loop by processing tasks listed in tasks/todo.md, generating a failing test first, writing minimal implementation code, validating the pass, and refactoring through enforced checkpoints.

What is the failing-test-first workflow for feature development and bug fixes?

The failing-test-first workflow requires writing a failing test before implementation, executing tests automatically, applying minimal code changes to pass, and refactoring with per-task checkpoints to maintain accountability.

Do I need to use a tasks/todo.md file to manage my TDD workflow?

Yes, a tasks/todo.md file is required because the skill drives the development loop by sequentially executing and checkpointing tasks listed specifically within that file.

Can I use specifications in specs/ to inform required behavior during test-driven development?

Yes, specifications in specs/ optionally integrate with the TDD loop to inform required behavior, guiding the generation of failing tests and the minimal implementation needed to pass them.

What's the best way to maintain accountability during a TDD cycle?

The best way to maintain accountability during a TDD cycle is through user checkpoints between steps, confirming progress after failing test creation, minimal implementation, test verification, and task completion.