investigate

Identify root causes through evidence gathering and 3-strike hypothesis testing.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/indigoai-us/hq --skill investigate-indigoai-us
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/indigoai-us/hq/tree/main/template/.claude/skills/investigate
Command: npx skills add https://github.com/indigoai-us/hq --skill investigate-indigoai-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Root-cause debugging workflows can be error-prone and time-consuming; this Skill standardizes investigations to prevent guesswork.

Core Features & Use Cases

  • Structured Investigation: Guides a reader through Step 0 to Step 5 with disciplined evidence collection and classification.
  • 3-Strike Hypothesis Testing: Generates up to three testable hypotheses to validate root causes before changes.
  • DEBUG REPORT Output: Produces a comprehensive, shareable report documenting findings and recommendations.

Quick Start

Analyze a failing module by initiating a structured root-cause investigation and generating a debug report.

Frequently Asked Questions about investigate

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

FAQPage Schema
How do I find the root cause of a software bug?▼

To find the root cause of a software bug, you need a structured debugging workflow that gathers evidence and classifies patterns before proposing fixes. This approach uses a 3-strike hypothesis test to validate the exact source of the unexpected behavior.

What is the best way to structure an investigation for an incident?▼

The best way to structure an incident investigation is to follow a disciplined step-by-step process from Step 0 to Step 5. This ensures thorough evidence collection and culminates in a comprehensive DEBUG REPORT documenting your findings.

How do I stop guessing when debugging code?▼

To stop guessing when debugging code, apply a 3-strike hypothesis testing method that requires generating up to three testable hypotheses. This enforces evidence-based validation of root causes before you make any codebase changes.

Can I generate a report documenting a bug fix investigation?▼

Yes, you can generate a DEBUG REPORT documenting a bug fix investigation. This structured report standardizes your findings, pattern classifications, and recommendations into a shareable format for your engineering team.

Does root-cause debugging work for tracing unexpected behavior in codebases?▼

Root-cause debugging works effectively for tracing unexpected behavior in codebases by applying systematic evidence gathering. It enforces a structured workflow to correctly identify the underlying issue before any fixes are attempted.