skills.rest
spideynolove
spideynoloveCOMMUNITY
Explore all skills by this author →
Website𝕏@spideynoloveGitHub

rlm-tdd

Enforces RED-GREEN-REFACTOR test-driven development discipline during RLM Phase 3 implementation.

2|3|Updated Mar 13, 2026
Search Tags:#testing#tdd#implementation#test-driven development#red-green-refactor#rlm#regression test
One-click install
npx skills add https://github.com/spideynolove/claude-dotfiles --skill rlm-tdd-spideynolove
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rlm-tdd
Source: https://github.com/spideynolove/claude-dotfiles/tree/main/.agents-global/skills/rlm-workflow/skills/rlm-tdd
Command: npx skills add https://github.com/spideynolove/claude-dotfiles --skill rlm-tdd-spideynolove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents production code from being written without a failing test first, eliminating unverified implementations and missing regression tests during RLM Phase 3 work. ## Core Features & Use Cases - Iron Law Enforcement: Blocks any production code that lacks a preceding failing test, with no exceptions for simple fixes or time pressure. - Structured TDD Cycle: Guides the full RED-GREEN-REFACTOR loop with mandatory verification that tests fail for the right reason before implementation. - Phase 3 Artifact Logging: Requires a TDD Compliance Log, coverage gate, and approval gate documenting every RED, GREEN, and REFACTOR step. - Use Case: When asked to fix a bug in an RLM run, the skill first demands a regression test that reproduces the crash, verifies the failure output, then permits only the minimal fix. ## Quick Start Ask the AI to implement a feature or fix a bug in RLM Phase 3 while following strict RED-GREEN-REFACTOR discipline with a failing test first.

Frequently Asked Questions about rlm-tdd

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

FAQPage Schema
How do I follow TDD when fixing a bug?▼

Write a regression test that reproduces the bug first and confirm it fails with the expected error. Then apply the minimal fix to make it pass, run the full test suite to check for regressions, and document each step in the Phase 3 artifact.

What is the RED-GREEN-REFACTOR cycle in test-driven development?▼

RED means writing one minimal failing test, GREEN means writing the simplest code to pass it, and REFACTOR means cleaning up while keeping tests green. You must watch the test fail before writing any production code.

Can I write code first and add tests afterward?▼

No. Tests written after code only confirm what the code does, not what it should do. If code was written before the test, the skill requires deleting it and restarting with a failing test first.

Why does my test passing immediately indicate a problem?▼

A test that passes immediately proves nothing because you never saw it catch the missing behavior. It usually means the test targets the wrong thing, tests mock behavior, or the feature already exists.

Are there exceptions to TDD for simple or urgent changes?▼

No exceptions exist for simple fixes, time pressure, or manual verification. The skill treats every excuse as a process shortcut and requires the full RED-GREEN-REFACTOR cycle for all behavior changes.

Related Skills

Explore More Software Engineering Skills→
roaming-rockenfelsroaming-rockenfels

feature-planning-tdd

Generate a TDD plan with acceptance criteria and failing tests before code.

Community
Advanced
easonlaoeasonlao

smoke-check

Run automated tests and interactive smoke checks into a PASS/FAIL report.

Community
Advanced
habit-hookshabit-hooks
40

habit-hooks-review

Detects hidden correctness bugs, design flaws, and missing test coverage in change sets after linting passes.

Official
Intermediate
ewe-studiosewe-studios
1

Rust Testing Excellence

Create Rust unit, integration, and property-based tests with proptest.

Official
Advanced