One-click install
npx skills add https://github.com/leocosta/octopus --skill test-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-tdd
Source: https://github.com/leocosta/octopus/tree/main/skills/test-tdd
Command: npx skills add https://github.com/leocosta/octopus --skill test-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Isolated TDD loop enables rapid iteration on small changes without requiring the full implement workflow, preventing scope creep and enabling safe regression fixes.

Core Features & Use Cases

  • Standalone four-phase loop (Plan → Tracer Bullet → Loop → Refactor) to drive one behavior per slice.
  • Enforces red-before-green discipline and prevents horizontal slicing for reliable refactors.
  • Integrates with other skills (implement, debug, test-e2e) to provide a focused unit of work without invoking the full end-to-end workflow.

Quick Start

Run the test-tdd loop on a bug fix to execute a red-green-refactor cycle.

Frequently Asked Questions about test-tdd

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

FAQPage Schema
How do I run an isolated test-driven development loop for small bug fixes?

An isolated test-driven development loop automates red-green-refactor cycles for small bug fixes. It executes a four-phase process—plan, tracer bullet, loop, refactor—to iterate rapidly on small changes without requiring a full feature workflow.

What is the red-green-refactor cycle in unit testing?

The red-green-refactor cycle in unit testing requires writing a failing test first, making it pass with minimal code, then cleaning up the implementation. This approach enforces test-first discipline and enables safe regression fixes during debugging sessions.

Can I use a standalone TDD loop for regression testing without a full feature workflow?

Yes, a standalone TDD loop handles regression testing without a full feature workflow. It prevents scope creep by focusing on isolated refactors and small bug fixes, enabling rapid iteration on individual behaviors.

Does test-driven development prevent horizontal slicing during software refactoring?

Test-driven development prevents horizontal slicing by enforcing a structured four-phase loop that drives one behavior per slice. This discipline ensures refactoring remains vertical and focused, keeping changes isolated and reliable.

What's the best way to integrate a TDD loop with end-to-end testing workflows?

The best way to integrate a TDD loop with end-to-end testing is to use it as a focused unit of work alongside other skills like implement, debug, and test-e2e. This provides isolated red-green-refactor cycles without triggering the full end-to-end workflow.