tdd

Name: tdd
Availability: InStock
Author: kasiopeiya

Automates Red-Green-Refactor cycles from issue files to final verification.

1|Updated Jan 18, 2026

Search Tags:#testing #tdd #development #agile #red-green-refactor #unit-testing

Ready to run

npx skills add https://github.com/kasiopeiya/oidc-learning-sandbox --skill tdd-kasiopeiya

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/kasiopeiya/oidc-learning-sandbox/tree/main/.claude/skills/tdd
Command: npx skills add https://github.com/kasiopeiya/oidc-learning-sandbox --skill tdd-kasiopeiya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD cycles are often manual and error-prone. This skill automates the end-to-end Red-Green-Refactor workflow from an issue file to a finished test and implementation, reducing cycle time and ensuring consistency.

Core Features & Use Cases

Automated TDD cycle execution: Orchestrates Red-Green-Refactor phases via the tdd-agent to guide incremental development.
Issue-driven design intake: Reads issues from docs/issues and related design/plan references to extract implementation specs.
Quality gate and reporting: Validates adherence to TDD principles, reports failures, and ensures tests pass before final verification.

Quick Start

Run /tdd with an Issue number or filename to begin the automated 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 TDD cycles from an issue file to finished unit tests?▼

Automated TDD cycle execution orchestrates the Red-Green-Refactor workflow across 7 phases, starting from issue load and ending with final test verification. It reads specs from docs/issues to guide incremental development.

How does issue-driven test generation work with design and plan references?▼

Issue-driven design intake reads from docs/issues and related design/plan references to extract implementation specs. These specs guide automated test generation and execution throughout the TDD cycle.

What is the best way to enforce strict adherence to TDD principles during agile development?▼

An automated quality gate validates adherence to TDD principles, reports failures, and ensures tests pass before final verification. This guarantees strict Red-Green-Refactor compliance throughout the workflow.

Can I use automated unit test execution for issues sourced from docs and design plans?▼

Yes, the automated TDD cycle applies to issues sourced from docs/issues, designs, and plan references. It executes unit tests and iteratively refactors the implementation based on those specs.

How do I start an automated Red-Green-Refactor workflow for a specific development issue?▼

Run the command with an Issue number or filename to begin the automated TDD cycle. This initiates the 7-phase workflow, loading the issue file and executing the Red-Green-Refactor sequence.

Why does iterative refactoring fail during automated test-driven development cycles?▼

Iterative refactoring fails when the quality gate detects non-compliance with TDD principles or when unit tests fail. The system reports these failures and blocks final verification until tests pass.