problem-analysis

Analyze inputs and symptoms to identify root causes of system failures.

42|3|Updated Mar 5, 2021

Search Tags:#debugging #investigation #root-cause #software-engineering #hypotheses #incident-analysis

Ready to run

npx skills add https://github.com/fmoda3/nix-configs --skill problem-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: problem-analysis
Source: https://github.com/fmoda3/nix-configs/tree/main/home/claude-code/config/skills/problem-analysis
Command: npx skills add https://github.com/fmoda3/nix-configs --skill problem-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies WHY a problem occurs by analyzing inputs, symptoms, and context to uncover the underlying cause.

Core Features & Use Cases

Iterative Hypothesis Generation: Proposes at least two distinct explanations and prioritizes evidence gathering.
Structured Investigation Phases: Guides through Gate, Hypothesize, Investigate, Formulate, and Output to a final root-cause statement.
Remediation Readiness: Produces a clear, actionable root-cause narrative ready for downstream solution steps.

Quick Start

Invoke the analysis script to start the investigation: python3 -m skills.problem_analysis.analyze --step 1

Frequently Asked Questions about problem-analysis

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

FAQPage Schema

How do I find the root cause of a software incident or system failure?▼

Root cause analysis identifies why a problem occurs by guiding you through structured investigation phases including Gate, Hypothesize, Investigate, Formulate, and Output to uncover the underlying cause from symptoms.

What is the best way to structure a debugging investigation when the underlying cause is unclear?▼

Structured debugging investigation works by applying iterative hypothesis generation to propose multiple explanations, validate them through gated evidence gathering, and output a final actionable root-cause statement.

Can I use this for incident analysis on complex software engineering failures?▼

Yes, this approach suits incident analysis for software engineering failures where the underlying cause is unclear, providing iterative hypothesis generation and gated validation to reach a final root-cause statement.

How do I start a root-cause analysis investigation using scripts?▼

Start a root-cause investigation by invoking the analysis script to initiate the first investigation step, guiding your inputs and symptoms through hypothesis generation to a final actionable root-cause statement.