rca

Name: rca
Availability: InStock
Author: rakovi4

Conduct structured root cause analysis by verifying hypotheses against real data.

45|13|Updated Apr 13, 2026

Search Tags:#quality assurance #root cause analysis #software debugging #evidence-based analysis #defect investigation

Ready to run

npx skills add https://github.com/rakovi4/continue-framework --skill rca-rakovi4

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rca
Source: https://github.com/rakovi4/continue-framework/tree/main/.claude/skills/rca
Command: npx skills add https://github.com/rakovi4/continue-framework --skill rca-rakovi4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents speculative problem-solving by ensuring that every cause of a defect is confirmed against real data through a structured root cause analysis process.

Core Features & Use Cases

Evidence-Based RCA: Verifies each hypothesis against real data, logs, and test runs.
Competing Hypotheses: Encourages listing multiple hypotheses to avoid biases.
Audit Prior Assumptions: Re-evaluates all existing claims and conclusions.
Workflow Documentation: Records findings in the task spec.md using a structured template.

Quick Start

To begin a root cause analysis, use the '/rca' command and provide the target bug task number or symptom.

Frequently Asked Questions about rca

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

FAQPage Schema

How do I conduct root cause analysis for software bugs without making assumptions?▼

Conduct root cause analysis by listing multiple competing hypotheses and verifying each one against real data, logs, and test runs. This structured approach ensures no assumptions are carried forward without verification, preventing speculative problem-solving.

What is the best way to document findings during a defect investigation?▼

Record defect investigation findings in the task spec.md using a structured template. This workflow documentation captures verified hypotheses, real data logs, and ruled-out assumptions to audit prior conclusions.

How does evidence-based analysis prevent speculative problem-solving for system failures?▼

Evidence-based analysis prevents speculative problem-solving by requiring every proposed cause of a system failure to be confirmed against real data. It audits prior assumptions and logs to ensure conclusions are verified.

Can I use root cause analysis for software bugs with multiple competing hypotheses?▼

Yes, you can analyze software bugs with multiple competing hypotheses by listing them to avoid biases and testing each one against real data. This ensures all existing claims are re-evaluated and ruled out systematically.

How do I start a root cause analysis for a specific bug task?▼

Start a root cause analysis by using the '/rca' command and providing the target bug task number or symptom. The Skill then structures the investigation, requiring real data verification for every hypothesis.