rlm-tdd

Enforce a RED-GREEN-REFACTOR workflow for RLM Phase 3 coding tasks.

4|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/try-works/rlm-workflow-acp --skill rlm-tdd-try-works
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rlm-tdd
Source: https://github.com/try-works/rlm-workflow-acp/tree/main/skills/rlm-tdd
Command: npx skills add https://github.com/try-works/rlm-workflow-acp --skill rlm-tdd-try-works

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Discipline ensures that every RLM Phase 3 change is guided by a test-first workflow, preventing production code without failing tests and embedding Phase 3 artifacts.

Core Features & Use Cases

  • Enforces RED-GREEN-REFACTOR cycle for Phase 3 coding tasks.
  • Provides triggers and guidance for writing failing tests before code and for recording TDD artifacts.
  • Applicable to features, bug fixes, and refactors with strict validation and traceability.

Quick Start

Initiate a Phase 3 TDD cycle by writing a failing test first, then implement the minimal green code, and finally refactor while keeping tests green.

Frequently Asked Questions about rlm-tdd

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

FAQPage Schema
How do I enforce a strict test-first TDD workflow for feature development and bug fixes?

The RED-GREEN-REFACTOR cycle starts by writing a failing test, then implementing the minimal code required to make it pass, and finally refactoring the code while ensuring all tests remain green.

Can I use test-driven development for refactoring existing code without breaking behavior?

Yes, test-driven development supports refactoring by keeping tests green throughout the process, ensuring that behavior changes are strictly validated and existing functionality is preserved.

What is the best way to prevent writing production code without a failing test during coding tasks?

The best way to prevent production code without a failing test is to enforce strict RED-GREEN-REFACTOR validation triggers that block implementation until a failing test is confirmed and recorded.

When do I need to record TDD artifacts during the software development lifecycle?

You need to record TDD artifacts during Phase 3 feature work, bug fixes, and refactors to embed traceability and ensure all changes align with safety standards and quality assurance requirements.

Does a strict RED-GREEN-REFACTOR workflow apply to all types of coding tasks?

Yes, the strict RED-GREEN-REFACTOR workflow applies to Phase 3 feature work, bug fixes, refactors, and behavior changes, guiding teams through test-first development cycles with strict validation.