One-click install
npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill rca-brucebanner010198-commits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rca
Source: https://github.com/brucebanner010198-commits/DevSecOps-Agency/tree/main/skills/rca
Command: npx skills add https://github.com/brucebanner010198-commits/DevSecOps-Agency --skill rca-brucebanner010198-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Root-cause analysis is essential for understanding security incidents, outages, and near-misses without assigning blame, enabling durable remediation and policy improvements.

Core Features & Use Cases

  • Structured, blameless postmortem framework using 5 Whys, Ishikawa (fishbone), and fault-tree analysis.
  • Timeline-driven investigation with required inputs, evidence, and traceability to reproduce findings.
  • Generates a formal RCA document, LESSONS row, and, when systemic issues are found, constitutional amendments or runtime-hook enhancements.
  • Use Case: after a Severity High incident, run RCA to identify root causes and prescribe concrete corrective actions with owners and due dates.

Quick Start

Run an RCA on the latest incident record using the incident data and log sources as inputs

Frequently Asked Questions about rca

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

FAQPage Schema
How do I conduct a blameless postmortem for a security incident?

A blameless postmortem identifies and documents root causes of security incidents without assigning blame, using a structured RCA framework to produce formal lessons and corrective actions. It applies Ishikawa analysis and fault-tree diagrams to uncover systemic issues.

What is the best way to structure an incident timeline for root cause analysis?

Root cause analysis requires a step-by-step timeline driven by incident data and log sources to ensure evidence traceability and reproduce findings. This timeline provides the formal structure needed to isolate systemic failures and prescribe concrete corrective actions with owners and due dates.

Can I use Ishikawa and fault-tree analysis together for outage investigation?

Ishikawa and fault-tree analysis are applied together within the blameless RCA framework to investigate outages and near-misses. This combined approach enables barrier analysis and identifies systemic root causes, resulting in formal RCA documents and actionable lessons learned.

When do I need a formal RCA document with corrective actions?

A formal RCA document with corrective actions is needed after a Severity High incident, security breach, or policy violation to ensure durable remediation. It satisfies requirements for step-by-step timelines, Ishikawa analysis, and fault-tree diagrams to prevent recurrence.

Does root cause analysis work for near-misses and Keeper Tests?

Root cause analysis works for near-misses, Keeper Tests, and policy violations by applying the same blameless postmortem framework used for security incidents and outages. It generates a formal RCA, LESSONS row, and constitutional amendments when systemic issues are found.