pelizzai-tdd

Implement features and bug fixes through red-green-refactor vertical slices.

Updated Jun 26, 2026

Search Tags:#automation #testing #tdd #refactoring #quality #engineering

Ready to run

npx skills add https://github.com/rpelizza/PelizzAI --skill pelizzai-tdd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pelizzai-tdd
Source: https://github.com/rpelizza/PelizzAI/tree/main/.agents/skills/pelizzai-tdd
Command: npx skills add https://github.com/rpelizza/PelizzAI --skill pelizzai-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents the common pitfalls of horizontal slicing and speculative coding by enforcing a rigorous, behavior-driven test-first discipline that ensures every line of code is justified by a failing test.

Core Features & Use Cases

Vertical Slicing: Implements features through tracer bullets, ensuring each test walks the system's real path.
Suitability Gate: Provides a structured decision framework to determine when TDD is appropriate versus when alternative strategies like characterization or visual QA are required.
Use Case: When implementing a new API endpoint, use this skill to define the public interface and behavior through a failing test before writing any implementation code, ensuring the design is driven by actual requirements.

Quick Start

Use the pelizzai-tdd skill to implement the new user authentication feature using a red-green-refactor cycle.

Frequently Asked Questions about pelizzai-tdd

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

FAQPage Schema

How do I enforce test-first discipline when building new features?▼

Test-first discipline is enforced by adhering to rigorous red-green-refactor cycles, ensuring every line of code is justified by a failing test before implementation begins. This prevents speculative coding and ensures behavioral verification.

What is vertical slicing in test-driven development?▼

Vertical slicing in test-driven development implements features through tracer bullets, ensuring each test walks the system's real path rather than isolating horizontal layers. This guarantees architectural integrity and behavioral verification.

How do I know when to use TDD versus other testing strategies?▼

A suitability gate provides a structured decision framework to determine when TDD is appropriate versus when alternative strategies like characterization testing or visual QA are required for your specific engineering task.

How do I implement an API endpoint using a red-green-refactor cycle?▼

To implement an API endpoint, define the public interface and behavior through a failing test before writing any implementation code, ensuring the design is driven by actual requirements and verified through the red-green-refactor cycle.

Why does speculative coding cause problems in software engineering?▼

Speculative coding causes problems by introducing unverified behavior and horizontal slicing pitfalls. Enforcing a behavior-driven test-first discipline ensures every line of code is justified by a failing test, preventing these architectural issues.

When should I not use test-driven development for bug fixing?▼

You should not use test-driven development when your task falls outside the suitability gate, indicating that alternative strategies like characterization testing or visual QA are more appropriate for verifying the specific behavior.