tdd

Automate TDD red-green-refactor cycles with vertical slicing and quality gates.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/jupes/agent-forge-harness --skill tdd-jupes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/jupes/agent-forge-harness/tree/main/.claude/skills/tdd
Command: npx skills add https://github.com/jupes/agent-forge-harness --skill tdd-jupes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill facilitates efficient test-driven development (TDD) by automating red-green-refactor cycles in vertical slices, ensuring behavior-first tests and robust quality gates.

Core Features & Use Cases

  • Vertical Slice TDD: Supports TDD in vertical slices, ensuring behavior-first testing and reducing complexity.
  • Quality Gates: Enforces type checks, lints, and testing after changes to maintain code quality.
  • Beads Integration: Integrates with Beads for task tracking, allowing for easy logging of progress.

Quick Start

To start a TDD slice, use the 'tdd' skill to create a new test for a specific behavior: 'start tdd slice "feature: <behavior>'. Then, run the cycle: 'execute tdd cycle'.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I automate test-driven development cycles for vertical slices?

Automating test-driven development cycles for vertical slices involves executing red-green-refactor workflows with behavior-first tests and robust quality gate checks. This Skill automates that process, enforcing type checks, lints, and testing after changes to maintain code quality.

What is behavior-first testing in vertical slices?

Behavior-first testing in vertical slices is an approach that writes tests targeting specific behaviors before implementation, reducing complexity. It ensures each slice delivers end-to-end functionality while maintaining strict quality gates throughout the TDD cycle.

How do I enforce quality gates during TDD automation?

Enforcing quality gates during TDD automation requires running type checks, lints, and tests after every code change. This Skill automatically validates these gates within the red-green-refactor cycle to maintain code quality before progression.

Can I integrate TDD automation with issue tracking systems?

Yes, you can integrate TDD automation with issue tracking systems. This Skill integrates with Beads for task tracking, allowing you to log progress and manage test-driven development slices directly alongside your issue tracking workflow.

How do I start a TDD slice for a specific behavior?

To start a TDD slice for a specific behavior, use the command to create a new test targeting that behavior, then execute the TDD cycle. This initiates the automated red-green-refactor workflow with quality gate enforcement.

Does this approach work without manual test maintenance?

This approach minimizes manual test maintenance by automating the red-green-refactor cycles and enforcing quality gates automatically. However, you still need to define the target behavior when starting each vertical slice for the automation to proceed.