Skill UI

Test-Driven Development (TDD) is a software development methodology where tests are written before the actual code. It follows the Red-Green-Refactor cycle to ensure code quality and reliability. Use this skill when implementing new logic, fixing bugs, or modifying existing functionality to prove correctness. It helps prevent regressions and creates a robust codebase suitable for AI agents.

This guide implements the Red-Green-Refactor cycle, the core methodology of Test-Driven Development (TDD). It teaches developers to first write a failing test (RED), then implement the minimum required code to make the test pass (GREEN), and finally improve the structure and clarity of the code without changing its behavior (REFACTOR). Use this guide when mastering TDD, ensuring robust unit test coverage, or following best practices for writing resilient software.

Applies proven testing patterns (AAA, Given-When-Then, builders, spies, doubles) to help write maintainable unit, integration, and end-to-end suites, covering structuring, naming, TDD/BDD, and mocks across frameworks like Jest, Vitest, or pytest.

Execute an implementation plan inline in the current session, task by task, using TDD and a durable ledger instead of per-task subagents. Choose it when your partner picks inline execution or no subagent tools exist. Covers briefs, rulings, completion contracts and final branch review.

Implements approved development tasks using Test-Driven Development methodology with autonomous or manual sub-agent dispatch. Supports multiple review modes (required/inline/off) and integrates with project specifications, requirements, and design documents for comprehensive implementation validation. Automatically discovers validation commands and establishes repository baselines before execution.

Test-Driven Development (TDD) is a development methodology that emphasizes writing failing tests first, followed by writing minimal code to pass them (Red -> Green), and finally refactoring the code (Refactor). This approach ensures that code is always verified against its intended public behavior, making the system robust, maintainable, and resilient to internal changes. It teaches developers to focus on 'what' the system does, rather than 'how' it does it.

This skill guides a systematic process for debugging reported issues. It explores the codebase to identify the root cause, traces the code path, and then generates a comprehensive GitHub issue. The fix plan strictly follows the Test-Driven Development (TDD) Red-Green cycle, ensuring proposed solutions are robust and durable, surviving major refactors.

This skill generates detailed implementation plans for multi-step tasks based on specifications before coding begins. It defines file structures, task granularity, and step-by-step instructions (TDD approach) to ensure clarity and testability. It includes self-check mechanisms and execution handoff options for AI agents or developers.

This skill guides users on creating, editing, and validating AI agent skills using Test-Driven Development (TDD) principles. It covers skill types, directory structure, SKILL.md formatting, and optimization strategies for discovery.

This comprehensive guide serves as a decision flowchart for developers using Claude Code. It details when to use specific slash commands (/plan, /compact, /loop), select specialized agents (planner, code-reviewer, build-error-resolver), or invoke workflow skills (e2e-testing, tdd-workflow). It helps users select the optimal tool combination for complex tasks across the entire software development lifecycle, including feature planning, bug fixing, testing, and architectural design.

A comprehensive guide to Test-Driven Development (TDD) for Quarkus 3.x services, focusing on achieving high coverage (80%+). It covers unit testing with Mockito, integration testing of REST endpoints, and advanced testing of event-driven architectures using Apache Camel and RabbitMQ.

This skill helps manage and execute steps within a Test-Driven Development (TDD) workflow cycle. Note that this skill serves as an alias for `tdd-workflows-tdd-cycle`, maintaining discoverability. It guides users through the complete TDD development cycle, ensuring structured testing and validation steps.