rlm-debugging

Perform systematic root-cause analysis for RLM bug-fix and failing-test requirements.

4|Updated Mar 17, 2026

Search Tags:#debugging #reproducibility #root-cause #bug-fix #data-flow #rlm #phase-1-5

Ready to run

npx skills add https://github.com/try-works/rlm-workflow-acp --skill rlm-debugging-try-works

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rlm-debugging
Source: https://github.com/try-works/rlm-workflow-acp/tree/main/skills/rlm-debugging
Command: npx skills add https://github.com/try-works/rlm-workflow-acp --skill rlm-debugging-try-works

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when RLM requirement involves debugging a bug, test failure, or unexpected behavior. Insert Phase 1.5 between Phase 1 and Phase 2 to perform systematic root cause analysis before attempting any fixes. Trigger phrases: "debug", "investigate", "failing tests", "crash", "root cause".

Core Features & Use Cases

Phase 1.5 Insertion is used between Phase 1 (AS-IS) and Phase 2 (TO-BE Plan) when debugging is required, ensuring a formal root-cause investigation precedes planning. The Four Phases of Systematic Debugging guide practitioners through Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and a structured Fix Summary to hand off to Phase 2.

Quick Start

Describe the bug, reproduce it, and generate the Phase 1.5 root-cause artifact before planning a fix.

Frequently Asked Questions about rlm-debugging

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

FAQPage Schema

How do I perform root-cause analysis for failing tests before planning a fix?▼

Systematic root-cause analysis is performed by reproducing the bug, tracing data-flow, testing hypotheses, and gathering evidence before planning fixes. This process inserts a formal debugging phase to investigate unexpected behavior and drive subsequent planning.

When should I use systematic debugging for bug-fix requirements?▼

Use systematic debugging for bug-fix requirements when you encounter failing tests, crashes, or unexpected behavior. It should be triggered when you need to investigate root causes and verify reproducibility before transitioning to the planning phase of your workflow.

What is the best way to trace data-flow and verify reproducibility for a bug?▼

The best way to trace data-flow and verify reproducibility is through a structured root-cause investigation. This involves reproducing the issue, analyzing patterns, and testing hypotheses to document concrete evidence that drives your fix planning.

Can I insert a debugging phase between AS-IS analysis and TO-BE planning workflows?▼

Yes, you can insert a dedicated debugging phase between AS-IS analysis and TO-BE planning workflows. This intermediate phase performs root cause investigation, pattern analysis, and evidence gathering to ensure fixes are planned based on verified hypotheses.

What phases are involved in systematic root-cause debugging?▼

Systematic root-cause debugging involves four phases: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and a structured Fix Summary. These phases guide practitioners from initial bug reproduction to a documented handoff for fix planning.