systematic-debugging

Diagnose repeated multi-agent task failures using a four-phase debugging methodology.

6|3|Updated Feb 11, 2026

Search Tags:#troubleshooting #defense-in-depth #debug #multi-agent #systematic #escalation #root-cause

Ready to run

npx skills add https://github.com/vinhnxv/rune-plugin --skill systematic-debugging-vinhnxv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/vinhnxv/rune-plugin/tree/main/plugins/rune/skills/systematic-debugging
Command: npx skills add https://github.com/vinhnxv/rune-plugin --skill systematic-debugging-vinhnxv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams systematically identify and trace root causes of repeated task failures in multi-agent workflows, reducing guesswork and speeding recovery.

Core Features & Use Cases

Phase-driven diagnosis: Observe, Narrow, Hypothesize, and Fix with structured outputs.
Cross-agent collaboration guidance: Includes checks like git blame, task dependencies, and escalation paths.
Use Case: When a worker fails a task three times, or a mend-fixer cannot reproduce a finding, this skill guides the debugging process and generates actionable steps.

Quick Start

Use the skill to start the four-phase debugging workflow on the current failure and follow Phase 1 instructions to collect evidence.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I find the root cause of repeated task failures in multi-agent workflows?▼

To find the root cause of repeated task failures in multi-agent workflows, apply a systematic four-phase debugging methodology: Observe, Narrow, Hypothesize, and Fix. This structured approach replaces guesswork with evidence collection, cross-agent checks, and escalation paths to pinpoint failures.

What is the best way to debug distributed agents when a worker keeps failing?▼

The best way to debug distributed agents that fail repeatedly is to trigger a systematic debugging workflow after three worker failures. This initiates phase-driven diagnosis, applying cross-agent collaboration checks like git blame and task dependency analysis to isolate the fault.

What steps are involved in the four-phase debugging process for distributed agents?▼

The four-phase debugging process for distributed agents involves Observe to collect evidence, Narrow to isolate variables, Hypothesize to identify the root cause, and Fix to apply the solution. Each phase generates explicit outputs and defensive recommendations.

How do I handle uncertain test-failure analyses across distributed agents?▼

To handle uncertain test-failure analyses across distributed agents, use a systematic debugging skill that provides structured escalation paths and cross-agent guidance. It helps verify findings when a mend-fixer cannot reproduce the issue, ensuring accurate root-cause identification.

Why does my multi-agent system still fail after applying a fix and running ward checks?▼

If ward checks fail after a fix in a multi-agent system, the initial repair likely missed the root cause. A systematic debugging approach addresses this by returning to evidence collection and hypothesis formation to ensure the underlying issue is fully resolved.