debug

Coordinate parallel hypothesis-investigator agents for ACH-based bug debugging.

6|3|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/vinhnxv/rune-plugin --skill debug-vinhnxv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/vinhnxv/rune-plugin/tree/main/plugins/rune/skills/debug
Command: npx skills add https://github.com/vinhnxv/rune-plugin --skill debug-vinhnxv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ACH-based parallel debugging. Spawns multiple hypothesis-investigator agents to investigate competing hypotheses simultaneously. Use when bugs are complex, when single-agent debugging hits 3+ failures, or when root cause is unclear. Also triggers when test-failure-analyst returns LOW confidence during arc Phase 7.7.

Core Features & Use Cases

  • ACH-based parallel hypothesis investigation to triage complex bugs with multiple competing explanations.
  • Multi-agent orchestration that distributes investigation tasks and collects evidence reports for arbitration.
  • Escalation and arc-triggered flows to handle low-confidence failure analyses and tie-breaker scenarios.

Quick Start

Invoke /rune:debug with a bug description to launch parallel hypothesis investigators.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug complex software bugs when single-agent investigation keeps failing?

Parallel multi-agent debugging investigates complex bugs by spawning multiple hypothesis-investigator agents simultaneously. It uses ACH-based analysis to triage competing explanations, distributing investigation tasks to gather structured evidence when single-agent approaches hit repeated failures.

What is ACH-based analysis for tracing unclear root causes in software engineering?

ACH-based analysis traces unclear root causes by evaluating competing hypotheses in parallel. It coordinates multiple investigator agents to gather structured evidence simultaneously, ensuring deterministic arbitration across reports to identify the true cause of complex bugs.

When should I use parallel debugging instead of standard single-agent investigation?

Use parallel debugging when bugs are complex, root causes are unclear, or single-agent debugging hits three or more failures. It also triggers escalation flows when failure analysis returns low confidence, requiring tie-breaker scenarios and structured evidence gathering.

How do I start an automated multi-agent investigation for a tough bug?

Start automated multi-agent investigation by providing a bug description to launch parallel hypothesis investigators. The system orchestrates multiple agents, distributes investigation tasks, and collects evidence reports for deterministic arbitration to resolve the issue.

Does multi-agent debugging work for triaging bugs with multiple competing explanations?

Multi-agent debugging works for triaging bugs with multiple competing explanations by applying ACH-based parallel hypothesis investigation. It orchestrates agents to evaluate each explanation simultaneously, ensuring structured evidence collection and deterministic arbitration across investigator reports.

What are the limitations of using parallel hypothesis investigators for debugging?

Parallel hypothesis investigators are limited when bugs are simple or single-agent debugging succeeds quickly. This approach targets complex scenarios with unclear root causes or low-confidence failure analyses, making it excessive for straightforward, easily traceable software issues.