investigate

Investigate production incidents through a four-phase root-cause debugging process.

Updated Mar 18, 2026

Search Tags:#troubleshooting #debug #investigate #root-cause #forensics #incident #systems

Ready to run

npx skills add https://github.com/ignidus/iscagent --skill investigate-ignidus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/ignidus/iscagent/tree/main/skills/investigate
Command: npx skills add https://github.com/ignidus/iscagent --skill investigate-ignidus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic approach to root-cause debugging and incident investigation to prevent superficial fixes.

Core Features & Use Cases

Four-phase methodology: gather symptoms, pattern analysis, hypothesis testing, and fix verification to ensure root causes are found before fixes.
Applies to production incidents, deployment failures, Terraform drift, and infrastructure issues.
Provides step-by-step guidance for documenting symptoms, testing hypotheses, and escalating when needed.

Quick Start

Initiate the four-phase investigation on the current incident and begin collecting symptoms and initiating root-cause analysis.

Frequently Asked Questions about investigate

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

FAQPage Schema

What is root-cause debugging and why is a systematic investigation process important?▼

Root-cause debugging systematically identifies the actual source of incidents rather than applying superficial fixes. A structured investigation prevents recurring issues by enforcing evidence gathering, pattern analysis, hypothesis testing, and fix verification before resolving production incidents.

How do I investigate Terraform drift and infrastructure deployment failures?▼

To investigate Terraform drift and infrastructure deployment failures, initiate a four-phase methodology: gather symptoms, analyze patterns, test hypotheses against evidence, and verify fixes. This structured approach ensures root causes are identified before applying changes to cloud environments.

What's the best way to debug production incidents without causing premature fixes?▼

The best way to debug production incidents without premature fixes is enforcing a four-phase investigation: collect symptoms, perform pattern analysis, test hypotheses, and verify fixes. This evidence-based approach prevents superficial patches from masking the true root cause.

Can I use a structured investigation methodology for cloud infrastructure issues across different environments?▼

Yes, this structured investigation methodology applies directly to cloud infrastructure issues across environments. It handles production incidents, deployment failures, and Terraform drift by standardizing symptom documentation, hypothesis testing, and escalation procedures for evidence-based conclusions.

How do I start a root-cause analysis when a production incident occurs?▼

Start root-cause analysis by initiating the four-phase investigation process on the current incident. Begin collecting symptoms immediately, then progress through pattern analysis, hypothesis testing, and fix verification to ensure evidence-based conclusions before applying any patches.

When should I escalate during an incident investigation?▼

You should escalate during incident investigation when evidence gathered through symptom collection, pattern analysis, and hypothesis testing is insufficient to determine a root cause. The methodology provides step-by-step guidance for documenting when escalation is necessary for complex infrastructure issues.