se-tdd

Guide the red-green-refactor loop for test-driven development workflows.

Updated May 7, 2026
One-click install
npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: se-tdd
Source: https://github.com/simonwjackson/pi-software-engineering/tree/main/skills/se-tdd
Command: npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development provides a disciplined approach to building software by writing tests before code and focusing on public interfaces to guide design, safety, and maintainability.

Core Features & Use Cases

  • Guided TDD loop: Walks through red, green, and refactor cycles to drive feature development and bug fixes.
  • Integration-test focus: Emphasizes end-to-end validation via integration-style tests rather than white-box checks.
  • Incremental, vertical slices: Encourages small, test-first increments aligned with user-visible behaviors.

Quick Start

Write a single end-to-end test that exercises a public API and implement the minimal code to pass it.

Frequently Asked Questions about se-tdd

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

FAQPage Schema
How do I automate the red-green-refactor loop for test-driven development?

You can automate the red-green-refactor loop by using a workflow that guides you through writing failing tests first, implementing minimal code to pass them, and then refactoring. This enforces disciplined, incremental feature development.

What is the best way to write integration-style tests for vertical slices?

The best way to write integration-style tests for vertical slices is to focus on end-to-end validation of public APIs. This approach encourages building small, test-first increments aligned with user-visible behaviors rather than relying on white-box checks.

Can I use test-driven development for fixing bugs and building features?

Yes, test-driven development applies to both feature development and bug fixes. By writing a failing test that captures the desired behavior or the specific bug, you can implement minimal code changes to make the test pass and safely refactor.

Does test-driven development work with tracer bullet workflows?

Yes, test-driven development supports tracer bullet workflows by encouraging end-to-end validation through minimal, test-driven changes. This allows you to build thin, vertical implementations that connect entire systems quickly.

When should I use integration tests instead of white-box checks in TDD?

You should use integration tests instead of white-box checks when you want to validate end-to-end behaviors through public APIs. This ensures your tests focus on user-visible outcomes and system interactions rather than internal implementation details.

Why does my test-driven development workflow require incremental implementation?

Test-driven development requires incremental implementation to ensure every code change is guarded by minimal, test-first increments. This approach maintains safety and maintainability by validating small, vertical slices of user-visible behavior continuously.