Execute TDD cycles with interface-first design and peer review.
npx skills add https://github.com/sei-newbear/xp-harness --skill slice-tdd
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
This Skill streamlines the implementation phase of software development using Test-Driven Development (TDD) cycles, fostering collaboration and high-quality code output.
To initiate a TDD cycle for implementing a feature, run the command: slice-tdd start feature-name
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
c-dalyAutomate a TDD-driven development loop with phase gates coordinating subagents.
tarrragonExtract Phase 4 technical debt from evaluation reports into Atomic Tickets.
webdriverioEnforce global validation across codebases with repository-wide checks.
alexsandrocruzEnforce test-driven development with red-green-refactor cycles and failing tests first.
