tdd

Automate test-driven development planning and execution for software features.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/prestarius/jet-skills-stack --skill tdd-prestarius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/prestarius/jet-skills-stack/tree/main/skills/tdd
Command: npx skills add https://github.com/prestarius/jet-skills-stack --skill tdd-prestarius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD helps teams deliver reliable software by forcing a failing-test first approach, ensuring each feature slice starts from a known failing state and ends with a passing test.

Core Features & Use Cases

  • Red-Green-Refactor workflow: repeatedly write failing tests, implement just enough code, and refactor.
  • Vertical-slice delivery: focus on the smallest complete behavior for fast feedback.
  • Guardrails for disciplined iteration: maintain test coverage and incremental progress.

Quick Start

Start by selecting a thin vertical slice, write a failing test first, then implement just enough code to make it pass and refactor.

Frequently Asked Questions about tdd

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

FAQPage Schema
What is test-driven development and how does the red-green-refactor cycle work?

Test-driven development enforces a red-green-refactor cycle where you write a failing test first, implement minimal code to pass it, then refactor. This iterative verification ensures each feature slice starts from a known failing state and ends with a passing test.

How do I automate test-first delivery for incremental software features?

Automating test-first delivery involves planning vertical slices, enforcing failing test creation, implementing minimal logic, and refactoring with repeatable verification. This disciplined incremental delivery workflow maintains test coverage and drives feature development iteratively.

How do I start applying TDD to a thin vertical slice of my software?

Start applying TDD by selecting the smallest complete behavior slice, writing a failing test first, implementing just enough code to make it pass, and refactoring. This ensures fast feedback and disciplined incremental progress.

Does test-driven development work for small vertical slices in feature development?

Test-driven development works effectively for small vertical slices in feature development. It focuses on the smallest complete behavior for fast feedback, enforcing red-green-refactor cycles and guardrails that maintain test coverage during iterative delivery.

What's the best way to maintain test coverage during iterative refactoring?

The best way to maintain test coverage during iterative refactoring is enforcing a test-first approach with red-green-refactor cycles. Guardrails ensure each feature slice ends with a passing test and repeatable verification before moving forward.