rai-debug

Diagnose software defects using triage, 5 Whys, and Ishikawa analysis.

71|8|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/humansys/raise --skill rai-debug-humansys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rai-debug
Source: https://github.com/humansys/raise/tree/main/packages/raise-cli/src/raise_cli/skills_base/rai-debug
Command: npx skills add https://github.com/humansys/raise --skill rai-debug-humansys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically identify and fix the root cause of defects using lean methods. Stop fixing symptoms — find the true cause.

Core Features & Use Cases

  • Triage and structured root-cause analysis (5 Whys, Ishikawa) to surface actionable fixes.
  • Guided workflow that records evidence, plan regression tests, and assigns prevention tasks.
  • Use Case: when a defect recurs after a fix, apply the steps to identify root cause and prevent recurrence.

Quick Start

Begin with triage and Genchi Genbutsu, then apply 5 Whys and Ishikawa to identify the root cause and implement a verified fix.

Frequently Asked Questions about rai-debug

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

FAQPage Schema
How do I find the root cause of a recurring software defect?

To find the root cause of a recurring defect, apply a structured triage workflow using 5 Whys and Ishikawa analysis. This method systematically surfaces actionable fixes instead of merely patching superficial symptoms.

What is the best way to triage production bugs where symptoms obscure the underlying cause?

The best way to triage production bugs is applying Genchi Genbutsu for direct evidence capture, followed by Ishikawa diagrams. This structured workflow isolates hidden root causes across development and production environments.

How do I perform 5 Whys root-cause analysis for software defects?

Perform 5 Whys root-cause analysis by starting with triage to capture evidence, then iteratively asking why the defect occurs. This guided workflow records findings and assigns prevention tasks to stop recurrence.

Why do my bug fixes fail to prevent defects from recurring in production?

Bug fixes fail to prevent recurring defects when only symptoms are patched. Applying lean methods like 5 Whys and Ishikawa analysis identifies the true root cause and enables verified, permanent fixes.

How do I plan regression tests after identifying a defect's root cause?

Plan regression tests after root-cause identification by using a structured defect-analysis workflow that records evidence and assigns prevention tasks. This ensures the verified fix addresses the true cause and prevents recurrence.

When should I use Ishikawa analysis for debugging instead of just fixing the reported error?

Use Ishikawa analysis for debugging when a defect recurs after a fix or when symptoms obscure underlying causes. It systematically maps contributing factors to ensure you fix the true root cause, not just symptoms.