Structured 4-phase debugging process enhanced with parallel diagnostics, root cause analysis, and optional reasoning tools.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Vodou Systematic Debugging - Parallel Diagnostic Workflow
## Overview
This skill provides **systematic debugging workflows** using a proven 4-phase process, enhanced by Vodou's parallel execution and **built-in memory** (retrieval + MEMORY.md / daily logs). There is no separate shipped codebase-analysis MCP—use memory plus your editor and tests.
**The Innovation**: Structured debugging process + parallel diagnostics = faster root cause identification.
**Based on**: Superpowers' `systematic-debugging` workflow, enhanced with Vodou's parallel execution.
---
## 4-Phase Debugging Process
### Phase 1: Reproduce and Isolate
**⏸️ STOPPING POINT - Understand the Problem**
Before debugging, understand the issue:
**"I'll help debug [issue]. Let me understand:**
1. **What is the problem?** (error message, unexpected behavior)
2. **When does it happen?** (always, sometimes, specific conditions)
3. **What were you doing?** (steps to reproduce)
4. **What's the expected behavior?** (what should happen)
**Can you describe the issue?"**
### Phase 1 Execution
**1. Reproduce the Issue**
```bash
# Try to reproduce
./do "run [command/script]"
./do "test [feature]"
```
…
The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_pmvpwgtrhel3ca6x
GET https://markdownregistry.com/api/v1/resolve?ref=vodouai/os/systematic-debugging
GET https://markdownregistry.com/api/v1/blob/66c2a3315f03f3474dbec7fc2f4c47814f64dc6b9450793d4eac6d302efd0512
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
vodouai/os · integrations/claude-code-plugin/skills/vodou-memory/SKILL.md · Use the user's Vodou memory — recall what they told any AI before, and save what matters now. Use when the user…
vodouai/os · integrations/claude-code-plugin/skills/vodou-setup/SKILL.md · Install or connect the Vodou engine so this plugin's memory tools and hooks work. Use when the session-start hook…
vodouai/os · skills/agents/design/visual-storyteller/SKILL.md · Visual storytelling agent that structures presentations, plans data visualizations, builds case study narratives, and…
vodouai/os · skills/agents/engineering/ai-engineer/SKILL.md · Expert AI engineer for LLM integration, RAG pipelines, prompt engineering, model evaluation, and AI agent development
mvschwarz/openrig · skills/_canonical/process/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
mvschwarz/openrig · packages/daemon/specs/agents/shared/skills/process/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
cbrock84/headcount · plugins/technology/skills/systematic-debugging/SKILL.md · Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever…
a5c-ai/babysitter · library/methodologies/superpowers/skills/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause…
