slice-tdd

Name: slice-tdd
Availability: InStock
Author: sei-newbear

Execute TDD cycles with interface-first design and peer review.

9|Updated May 11, 2026

Search Tags:#code quality #tdd #software development #test-driven development #peer review

Ready to run

npx skills add https://github.com/sei-newbear/xp-harness --skill slice-tdd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: slice-tdd
Source: https://github.com/sei-newbear/xp-harness/tree/main/.apm/skills/slice-tdd
Command: npx skills add https://github.com/sei-newbear/xp-harness --skill slice-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires slice-tdd, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the implementation phase of software development using Test-Driven Development (TDD) cycles, fostering collaboration and high-quality code output.

Core Features & Use Cases

TDD Implementation: Execute the full TDD cycle (Red → Green → Refactor → Commit) for code writing, testing, refactoring, bug fixes, and E2E spec additions.
Outside-In TDD: Emphasizes interface-first design, ensuring a solid foundation for the development process.
Collaboration: Integrates peer review through subagents for continuous improvement and validation.

Quick Start

To initiate a TDD cycle for implementing a feature, run the command: slice-tdd start feature-name

Frequently Asked Questions about slice-tdd

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

FAQPage Schema

How do I implement test-driven development cycles for new software features?▼

You can execute test-driven development cycles by running the slice-tdd start command with your feature name. This initiates the full Red, Green, Refactor, and Commit cycle, managing code writing, testing, and refactoring while emphasizing interface-first design.

What is outside-in TDD and how does interface-first design work?▼

Outside-in TDD emphasizes interface-first design, ensuring a solid foundation for the software development process. It defines external interfaces and behaviors before internal implementation, guiding the TDD cycle to build code that precisely meets integration requirements.

How do I integrate peer review into my TDD workflow?▼

Peer review integrates into your TDD workflow through subagents that validate code during the implementation process. This collaboration mechanism ensures continuous improvement and high-quality code output by triggering reviews automatically within the TDD cycle.

Can I use this TDD approach for bug fixes and end-to-end spec additions?▼

Yes, this TDD approach supports bug fixes and end-to-end spec additions alongside standard code writing and refactoring. It manages these tasks within the structured TDD cycle, ensuring all modifications meet the same testing and quality standards.

Does test-driven development work without initial interface design?▼

Test-driven development can work without initial interface design, but this Skill enforces outside-in TDD to prioritize it. Interface-first design ensures a solid foundation for the development process, preventing structural inconsistencies during the Red and Green phases.

What are the limitations of using subagents for peer review in software development?▼

Subagents for peer review are limited by their dependency on the slice-tdd skill for executing TDD cycles. While they validate code and foster collaboration, they cannot replace human judgment in complex architectural decisions during the refactoring phase.