Diagnose incident root causes using Five Whys and generate signed-off corrective actions.
npx skills add https://github.com/usurobor/cnos --skill rca-usurobor
Please help me install this Agent Skill. Skill: rca Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.eng/skills/eng/rca Command: npx skills add https://github.com/usurobor/cnos --skill rca-usurobor
Blameless Root Cause Analysis after incidents helps teams diagnose systemic failures without blaming individuals, preserving evidence, and guiding durable improvements. It ensures post-incident learning is thorough, objective, and actionable.
Create a new RCA thread and begin documenting the incident using the Five Whys method to identify the root cause.
High-intent search queries and answers about installing and using this skill.
Conduct blameless root cause analysis by capturing incident timelines and evidence, applying structured methods like Five Whys to identify systemic failures, and generating signed-off corrective actions to prevent recurrence.
Document an incident timeline for postmortems by capturing events and evidence chronologically to build a complete record, which preserves objective data for subsequent structured analysis and durable system improvements.
The Five Whys method works for incident management by sequentially asking why an event occurred to move past symptoms, identifying root causes without assigning blame, and converting findings into actionable corrective actions.
You can generate signed-off corrective action plans by completing structured analysis, assigning specific owners and due dates to preventive measures, and tracking these actions to ensure durable system improvements across teams.
Root cause analysis requires no specific dependencies or platforms to get started; you can create a new analysis thread and immediately begin documenting the incident using the Five Whys method.
Use blameless postmortems when you need to diagnose systemic failures objectively without blaming individuals, ensuring post-incident learning is thorough, actionable, and focused on durable improvements rather than personal fault.
ramybarsoumConvert raw incident notes into structured postmortem documents with RCA and action items.
45black-LimitedIdentify and document root causes using Ishikawa categories and Five Whys.
constellizeGenerate structured incident postmortems with executive summaries, timelines, and root cause analysis.
cathrynlaveryDiagnose root causes and evaluate solutions using structured analytical frameworks.
