Rca gen

Skill victoriacheng15/dev-toolchain/rca-gen

A portable library of standardized AI agent skills and orchestration scripts, built on the SKILL.md open standard to streamline consistent engineering workflows across diverse LLM clients.

Install

npx -y skills add victoriacheng15/dev-toolchain --skill rca-gen

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Guides the creation and management of Root Cause Analysis (RCA) records with chronological indexing.

SKILL.md

2.9 KB, as published. Nobody here has run it

Root Cause Analysis (RCA)

Overview

Root Cause Analysis (RCA) is a structured process to identify the underlying vulnerabilities that caused a system failure or incident. This skill standardizes the lifecycle of RCAs, ensuring that we learn from every failure, document technical debt, and prevent regression through systemic, architectural improvements.

Automated Execution

To create a new, auto-incremented RCA skeleton, execute the companion template generator from the root of the workspace:

./rca-gen/new-rca.sh "Title of the Incident"

This script scans the docs/incidents/ directory, detects the next sequential ID, and generates a pre-formatted template with standard metadata headers.

RCA Lifecycle States

Every RCA must transition through defined, explicit lifecycle states:

Investigating: The incident is under active investigation, or the document is currently being drafted.
Mitigated: The technical impact of the incident is stopped, but the long-term permanent fix is not yet complete.
Resolved: All follow-up actions, prevention plans, and verification tests have been fully completed and closed.

Mandatory RCA Template Structure

All RCA markdown files (e.g., docs/incidents/001-database-connection-exhaustion.md) must strictly adhere to the following schema:

# RCA XXX: [Descriptive Title]

- **Status:** [Investigating | Mitigated | Resolved]
- **Date:** [YYYY-MM-DD]
- **Severity:** [High | Medium | Low]
- **Author:** [Author Name]

## Summary

A brief overview of what happened, the impact, and the duration.

## Timeline

- **[YYYY-MM-DD HH:MM]:** Incident detected.
- **[YYYY-MM-DD HH:MM]:** Investigation started.
- **[YYYY-MM-DD HH:MM]:** Mitigation applied.
- **[YYYY-MM-DD HH:MM]:** Root cause identified.
- **[YYYY-MM-DD HH:MM]:** Permanent fix deployed.

## Root Cause Analysis

Detailed explanation of why the incident happened (The "Why").

## Lessons Learned (Optional)

What went well? What went wrong? What reduced the impact?

## Action Items

- [ ] **Fix:** Immediate technical resolution.
- [ ] **Prevention:** Changes to prevent recurrence (e.g., monitoring, tests).
- [ ] **Process:** Changes to workflows or documentation.

## Verification

- [ ] **Manual Check:**
- [ ] **Automated Tests:**

Verification Checklist

Prior to committing a new RCA, verify that:

State Specified: The metadata section contains an allowed lifecycle state.
Chronology Checked: The next sequential integer index has been reserved using the orchestration script.
Root Cause Analyzed: The technical explanation is explicitly written out to avoid superficial blame.
Action Items Assigned: Every action item in mitigation or prevention has clear, actionable definitions.