Tdd
This skill guides you through test-driven development using separate subagents for test writing and implementation, ensuring each phase stays focused on its role. It supports Jest, Vitest, pytest, Go test, cargo test, PHPUnit, and RSpec, with modes for interactive approval, autonomous execution, and dry-run validation. Vertical slicing and context isolation keep your TDD workflow disciplined and your tests honest.
Tdd enforces disciplined test-driven development by orchestrating separate agents for test writing and implementation to prevent specification leakage.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
Tdd enforces disciplined test-driven development by orchestrating separate agents for test writing and implementation to prevent specification leakage. This skill guides you through test-driven development using separate subagents for test writing and implementation, ensuring each phase stays focused on its role. It supports Jest, Vitest, pytest, Go test, cargo test, PHPUnit, and RSpec, with modes for interactive approval, autonomous execution, and dry-run validation. Vertical slicing and context isolation keep your TDD workflow disciplined and your tests honest.
Use it when
- TDD supports writing tests first through dedicated test-writing phases.
- TDD supports a wide range of testing frameworks across multiple languages: Jest and Vitest for JavaScript, pytest for Python.
Install
glebis/claude-skills/tdd · repository language: JavaScript
generated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What is test-driven development and how does TDD work?
TDD is a methodology where you write tests before implementing code. TDD guides you through this process using separate subagents for test writing and implementation, ensuring each phase stays focused on its role. The workflow follows the red-green-refactor cycle: write a failing test (red), implement code to pass it (green), then refactor for quality. This test-first approach improves code reliability by catching issues early.
How do I write tests first in TDD?
TDD supports writing tests first through dedicated test-writing phases. You define test cases before implementation, specifying what your code should do. TDD works with popular frameworks including Jest, Vitest, pytest, Go test, cargo test, PHPUnit, and RSpec. The skill uses separate subagents to keep test writing focused, ensuring your tests remain honest and properly isolated through context isolation and vertical slicing techniques.
What testing frameworks does TDD support?
TDD supports a wide range of testing frameworks across multiple languages: Jest and Vitest for JavaScript, pytest for Python, Go test for Go, cargo test for Rust, PHPUnit for PHP, and RSpec for Ruby. This broad framework support lets you apply test-driven development methodology regardless of your tech stack, with consistent red-green-refactor workflows across all supported platforms.
What modes does TDD offer for automated testing setup?
TDD provides three execution modes for your automated testing workflow: interactive approval mode lets you review and approve each step, autonomous execution runs the full red-green-refactor cycle automatically, and dry-run validation lets you preview changes without committing them. These modes support different team preferences while maintaining discipline through vertical slicing and context isolation.
How can TDD help improve code quality and reliability?
TDD improves code reliability through its test-first approach, which catches defects before they reach production. By writing test cases before implementation, you clarify requirements upfront and ensure comprehensive coverage. TDD's red-green-refactor cycle combined with separate subagents for testing and implementation keeps your workflow disciplined, while vertical slicing and context isolation ensure your tests remain focused and honest.
What is the red-green-refactor cycle in TDD?
The red-green-refactor cycle is the core TDD development pattern. Red: write a failing test that defines desired behavior. Green: write minimal code to make the test pass. Refactor: improve code quality without changing functionality. TDD guides you through this cycle repeatedly, using separate subagents to keep each phase focused. This structured approach ensures continuous testing and maintains code quality throughout development.
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Learn and implement test-driven development methodology”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Test Driven Development teaches the red-green-refactor discipline for writing code validated by tests before implementation. Learn when to apply TDD across feature work, bug fixes, and refactoring, plus how to design testable interfaces, mock at system boundaries, and avoid common pitfalls.
This skill activates during OpenSpec change implementation to enforce atomic test-driven development: every test—acceptance, unit, edge case, or helper—must fail for the right reason before production code is written to make it pass. Gherkin scenarios in spec.md are the canonical acceptance contract; every relevant scenario must become at least one test. The per-test state machine forbids batching, skipping refactor assessment, or shipping with uncovered scenarios.
tdd guides you through strict test-driven development using the red-green-refactor cycle: write a failing test, implement minimal code to pass it, then refactor. The skill enforces the discipline of writing tests before production code and provides framework-specific commands for multiple languages.
tdd guides you through writing tests before implementation using the red-green-refactor workflow. Each cycle commits a failing test marked red, then minimal passing code marked green, with refactoring only after all tests pass. The skill enforces behavioral testing over implementation details and includes commit hygiene checks to keep your tree lint-clean at every step.
rtk-tdd enforces the red-green-refactor cycle for Rust development, automatically guiding you through failing tests, minimal implementations, and refactoring phases. It provides Rust-idiomatic testing patterns using anyhow/thiserror, cfg(test) modules, and Arrange-Act-Assert workflows, with pre-commit gates ensuring code quality.
Testing guides you through designing effective test suites, writing unit and integration tests, and applying test-driven development practices. It covers test strategy, the AAA pattern, test fixtures, mocking dependencies, and framework-specific approaches for React, Angular, Python, Java, and Kotlin.