10x-tdd

Drive test-first development through the red-green-refactor cycle for new phases.

Updated Jun 9, 2024
One-click install
npx skills add https://github.com/Kuba312/daily-board --skill 10x-tdd-kuba312
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-tdd
Source: https://github.com/Kuba312/daily-board/tree/main/frontend/.agents/skills/10x-tdd
Command: npx skills add https://github.com/Kuba312/daily-board --skill 10x-tdd-kuba312

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured test-first development loop for new phases of a project, ensuring that the implementation is of high quality and adheres to test-driven principles.

Core Features & Use Cases

  • Test-First Development: Ensures each new phase of the project starts with writing a failing test.
  • Phase-by-Phase Execution: Drives the implementation through the red-green-refactor cycle, phase by phase.
  • Implementation Check: Stops the TDD loop if a phase's implementation already exists and suggests using /10x-implement.
  • Use Case: When a new phase of a project is ready for implementation, this Skill can be used to drive the development through TDD, ensuring the codebase is well-tested.

Quick Start

Execute the /10x-tdd <change-id> command to start the TDD loop for a new phase of your project.

Frequently Asked Questions about 10x-tdd

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

FAQPage Schema
How do I implement new development phases using a test-first approach?

Test-first implementation is driven through the red-green-refactor cycle phase by phase. You execute the command with a specified change ID to read the plan and Progress section, writing a failing test before production code exists.

When should I use a TDD loop versus standard implementation for a new phase?

A TDD loop is suitable for phases where production code does not yet exist. If a phase's implementation already exists, the loop stops and redirects to standard implementation to avoid redundant test-first cycles.

Do I need existing test infrastructure to run a test-driven development loop?

Existing test infrastructure is required to run the test-driven development loop. The Skill drives the cycle by checking TDD-ability and writing tests against your current setup before implementing the new phase.

How does phase-by-phase test-driven development handle phases that are not testable?

Phase-by-phase execution checks each phase for TDD-ability before proceeding. If a phase is not suitable for test-first development or already has implementation, it redirects to standard implementation.

What are the limitations of using a red-green-refactor cycle for project phases?

The red-green-refactor cycle is limited to new phases where production code does not exist yet. It cannot drive development if test infrastructure is missing, and it redirects to standard implementation for existing code.

How do I start a test-driven development loop for a specific project change?

To start the loop, execute the command with your specified change ID. This reads the development plan and Progress section to begin driving the implementation test-first through each phase.