investigate

Guide phase-based questioning to identify root causes of complex multi-system bugs.

1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/builtbylee/socratic-prompts --skill investigate-builtbylee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/builtbylee/socratic-prompts/tree/main/skills/investigate
Command: npx skills add https://github.com/builtbylee/socratic-prompts --skill investigate-builtbylee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Socratic debugger helps teams isolate root causes in complex, multi-system bugs by enforcing a disciplined, phase-based interrogation that distinguishes facts from interpretations and prevents premature fixes.

Core Features & Use Cases

  • Phase-guided debugging: Enforces Phase 1 through Phase 4 workflows to structure investigations.
  • Socratic questioning: Prompts targeted diagnostics to surface hidden causes without leaping to conclusions.
  • Repro-focused analysis: Emphasizes reproduction boundaries, null-hypothesis checks, and testable hypotheses to reduce guesswork.

Quick Start

Describe the bug and provide initial facts so the agent can begin Phase 1 analysis.

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 complex bug when symptoms are ambiguous?

A phase-based debugging workflow structures complex issue reproduction by guiding you through four interrogation phases, ensuring systematic root-cause isolation across multi-system interactions without leaping to conclusions.

Why do my prior fixes fail to resolve recurring multi-system bugs?

Prior fixes often fail because they target symptoms rather than root causes; enforcing phase-based questioning and null-hypothesis checks during issue reproduction prevents guesswork and verifies true root-cause resolution.

What is the best way to structure debugging diagnostics for difficult-to-reproduce issues?

The best way to structure debugging diagnostics is using a phase-guided workflow that emphasizes repro-focused analysis, testable hypotheses, and explicit facts versus interpretations to safely isolate hidden causes.

Can I use a Socratic questioning approach for diagnosing multi-system interactions?

Yes, you can use a Socratic questioning approach to diagnose multi-system interactions by applying targeted diagnostics that surface hidden causes and enforce structured, phase-based interrogation across ambiguous debugging scenarios.

When should I avoid using phase-based debugging workflows?

You should avoid phase-based debugging workflows for simple, isolated bugs with obvious causes and straightforward reproduction, as the structured Socratic interrogation and staged hypothesis generation are designed for complex, ambiguous diagnostics.