diagnose

Diagnose root causes of bugs and incidents through a four-phase investigation protocol.

2|Updated Oct 2, 2025
One-click install
npx skills add https://github.com/misty-step/volume --skill diagnose-misty-step
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/misty-step/volume/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/misty-step/volume --skill diagnose-misty-step

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Investigate, audit, triage, and fix. Systematic debugging, incident lifecycle, domain auditing, and issue logging. Four-phase protocol: root cause → pattern analysis → hypothesis test → fix.

Core Features & Use Cases

  • Structured, repeatable root-cause investigation workflow for complex incidents and bugs.
  • Reference-driven analysis using standardized guidance and templates to collect evidence.
  • Use cases span production incidents, flaky tests, audits, and postmortems with clear handoffs.

Quick Start

Initiate a four-phase investigation to identify and prove the root cause before applying fixes.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is systematic debugging and when do I need it for root-cause analysis?

Systematic debugging is a structured protocol to investigate and prove the root cause of bugs before fixing. You need it for production incidents, flaky tests, and domain audits requiring traceable evidence and clear handoffs.

How do I diagnose the root cause of a production incident?

To diagnose a production incident, initiate a four-phase protocol: root cause investigation, pattern analysis, hypothesis testing, and implementation. This structured workflow collects reference-driven evidence to enable rapid, verifiable fixes.

Can I use this systematic debugging approach for flaky test failures and postmortems?

Yes, this approach applies to flaky test failures and postmortems. It uses standardized guidance and templates to collect traceable evidence, ensuring structured root-cause investigation and clear handoffs across these scenarios.

What's the best way to investigate bugs without immediately applying fixes?

The best way to investigate bugs without premature fixes is following a four-phase protocol. It enforces pattern analysis and hypothesis testing to prove the root cause first, ensuring fixes are verifiable and correct.

Does this incident management workflow require any specific dependencies?

No specific dependencies are required for this incident management workflow. It uses internal references to provide standardized guidance and templates for collecting evidence throughout the four-phase investigation.