rg-tdd

Guide developers through red-green TDD cycles with failing tests and minimal fixes.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Jaggia/backTestingTraderBot --skill rg-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rg-tdd
Source: https://github.com/Jaggia/backTestingTraderBot/tree/main/.claude/skills/rg-tdd
Command: npx skills add https://github.com/Jaggia/backTestingTraderBot --skill rg-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers through a red-green TDD workflow for a codebase.

Core Features & Use Cases

  • Identify the target to test (function, class, or behavior) and write a failing test.
  • Implement the minimal code required to make the test pass, then refactor if needed.
  • Record tests and changes with clear commit messages and optional journal entries.
  • Provides templates and prompts to streamline red-green cycles across typical software-engineering tasks.

Quick Start

Start the RG-TDD workflow by saying /rg-tdd and follow the guided steps to write a failing test, implement the minimal fix, and commit both together.

Frequently Asked Questions about rg-tdd

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

FAQPage Schema
How do I start a red-green TDD workflow for my codebase?

Start the red-green TDD workflow by triggering the guided steps to identify your testing target, write a failing test, implement the minimal code fix to pass it, and commit both together with traceability.

What is the red-green TDD process for software engineering tasks?

The red-green TDD process enforces step-by-step test creation for a target behavior, followed by implementing the minimal code required to pass that test, and finally documenting changes with optional journal entries.

Does this TDD workflow provide templates for test scaffolding and progress logging?

Yes, this TDD workflow provides built-in templates and prompts to streamline red-green cycles, specifically aiding in test scaffolding, code changes, and progress logging across typical software-engineering tasks.

Can I use this guided TDD workflow to document code changes and journal entries?

Yes, you can use this guided TDD workflow to record tests and code changes, automatically enforcing committed traceability with clear commit messages and optional journal entries for your software-engineering tasks.

What's the best way to ensure minimal implementation during test-driven development?

The best way to ensure minimal implementation during test-driven development is to follow a guided red-green workflow that enforces writing a failing test first and implementing only the code required to make it pass.